Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73bcd7c44f594ab80b128d361404fb894e4cdaa9a05112fcbbebfe96de14f66

Tx prefix hash: b303232824df35ee5dbd3644c1d4862b83e919e46caf81e0eac970e54e6361cb
Tx public key: 32ab1b6be5f3c19890d458b28744c644603ae344b89c1ef37948f83186e5c314
Timestamp: 1696107591 Timestamp [UCT]: 2023-09-30 20:59:51 Age [y:d:h:m:s]: 01:147:16:12:27
Block: 859680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366556 RingCT/type: yes/0
Extra: 0132ab1b6be5f3c19890d458b28744c644603ae344b89c1ef37948f83186e5c31402110000000133af99f4000000000000000000

1 output(s) for total of 0.870008173000 dcy

stealth address amount amount idx
00: 1f2552e97810dec7058647f15c3203372d2e42fddc8494137b83efdaa5c75350 0.870008173000 1313920 of 0

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": 859690, "vin": [ { "gen": { "height": 859680 } } ], "vout": [ { "amount": 870008173, "target": { "key": "1f2552e97810dec7058647f15c3203372d2e42fddc8494137b83efdaa5c75350" } } ], "extra": [ 1, 50, 171, 27, 107, 229, 243, 193, 152, 144, 212, 88, 178, 135, 68, 198, 68, 96, 58, 227, 68, 184, 156, 30, 243, 121, 72, 248, 49, 134, 229, 195, 20, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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