Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 571dbb54358369fbbf331f01ae43ad3c93e2906f525d1396786a65d7264a559f

Tx prefix hash: 0eaf6fea9e4b3e75dc66e8a52360f3628cb0c44abad8f24897da99e42b7415aa
Tx public key: 17bd995b7b8a59f74a050599cd93301822d4c12ce6d51b6b752af1c0698d1ce0
Timestamp: 1723642183 Timestamp [UCT]: 2024-08-14 13:29:43 Age [y:d:h:m:s]: 00:212:09:51:26
Block: 1087753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151691 RingCT/type: yes/0
Extra: 0117bd995b7b8a59f74a050599cd93301822d4c12ce6d51b6b752af1c0698d1ce002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55a6c674722486cadaf33afa7aa76a075bfc95dc003370da8b812739c5c0dc32 0.600000000000 1562364 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1087763, "vin": [ { "gen": { "height": 1087753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55a6c674722486cadaf33afa7aa76a075bfc95dc003370da8b812739c5c0dc32" } } ], "extra": [ 1, 23, 189, 153, 91, 123, 138, 89, 247, 74, 5, 5, 153, 205, 147, 48, 24, 34, 212, 193, 44, 230, 213, 27, 107, 117, 42, 241, 192, 105, 141, 28, 224, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8