Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384ea9d0c72fb609344d914ddb80ee61c5837611e2755c90a5ea9e38555b884d

Tx prefix hash: 94989061548f5d9ecedc1860c8fb988eff2386d5558751e77e2e7c790fe384cc
Tx public key: 9c526f4ba087a2e7c52985b7adb2d3940868294ab56bba5983f78eae8a75ae96
Timestamp: 1717502701 Timestamp [UCT]: 2024-06-04 12:05:01 Age [y:d:h:m:s]: 01:010:06:45:02
Block: 1036863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268155 RingCT/type: yes/0
Extra: 019c526f4ba087a2e7c52985b7adb2d3940868294ab56bba5983f78eae8a75ae9602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74f2697e5d911119d488a33d4120c6721de96252f4d7ed01fb1c7ab728ea2983 0.600000000000 1505392 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": 1036873, "vin": [ { "gen": { "height": 1036863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74f2697e5d911119d488a33d4120c6721de96252f4d7ed01fb1c7ab728ea2983" } } ], "extra": [ 1, 156, 82, 111, 75, 160, 135, 162, 231, 197, 41, 133, 183, 173, 178, 211, 148, 8, 104, 41, 74, 181, 107, 186, 89, 131, 247, 142, 174, 138, 117, 174, 150, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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