Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd70dceae271ea4639634fbd4b9ece71bb3c41c3da1480d4fabcb064a222955

Tx prefix hash: 17e841f128ac1c2e49acd124ca7fdf03446ae581c54023fc70c2222393ebcb1b
Tx public key: bcd1d4dee1338f94a6c081c1e7a1d73d02e5a7a2620e46e8dc5d36a304e7583c
Timestamp: 1660108324 Timestamp [UCT]: 2022-08-10 05:12:04 Age [y:d:h:m:s]: 02:231:12:03:20
Block: 562586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686675 RingCT/type: yes/0
Extra: 01bcd1d4dee1338f94a6c081c1e7a1d73d02e5a7a2620e46e8dc5d36a304e7583c021100000003ec6d1a1a000000000000000000

1 output(s) for total of 8.393037340000 dcy

stealth address amount amount idx
00: 589256262318ddf552b95a76e019a5146d608d8172f1435598a91d8a6ccac72d 8.393037340000 995178 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": 562596, "vin": [ { "gen": { "height": 562586 } } ], "vout": [ { "amount": 8393037340, "target": { "key": "589256262318ddf552b95a76e019a5146d608d8172f1435598a91d8a6ccac72d" } } ], "extra": [ 1, 188, 209, 212, 222, 225, 51, 143, 148, 166, 192, 129, 193, 231, 161, 215, 61, 2, 229, 167, 162, 98, 14, 70, 232, 220, 93, 54, 163, 4, 231, 88, 60, 2, 17, 0, 0, 0, 3, 236, 109, 26, 26, 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