Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6935c457c87122e215966a4732ece1ab68969dcbe6a61f34cf7a561162ffff14

Tx prefix hash: c006942523affe3147dcb6d40a59752fa8d793d81f9f492a6ce8c30a38333589
Tx public key: 4bdc971a6437e696c25263d1ae5dcf662fd7be0fa2a9fe231d4d58c059d2da43
Timestamp: 1694044447 Timestamp [UCT]: 2023-09-06 23:54:07 Age [y:d:h:m:s]: 01:170:20:45:15
Block: 842549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383189 RingCT/type: yes/0
Extra: 014bdc971a6437e696c25263d1ae5dcf662fd7be0fa2a9fe231d4d58c059d2da43021100000002faf35c9c000000000000000000

1 output(s) for total of 0.991483456000 dcy

stealth address amount amount idx
00: 7e42aa3eb610291553d07bcbfc6bc1aa1d4c0f2d0af7f33cfe3580e78e408dc9 0.991483456000 1295681 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": 842559, "vin": [ { "gen": { "height": 842549 } } ], "vout": [ { "amount": 991483456, "target": { "key": "7e42aa3eb610291553d07bcbfc6bc1aa1d4c0f2d0af7f33cfe3580e78e408dc9" } } ], "extra": [ 1, 75, 220, 151, 26, 100, 55, 230, 150, 194, 82, 99, 209, 174, 93, 207, 102, 47, 215, 190, 15, 162, 169, 254, 35, 29, 77, 88, 192, 89, 210, 218, 67, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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