Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d5164c552b091aacc77c05a387baa874cc5ea2fe49ea62ede0f07549c1bb0d7

Tx prefix hash: ca443fe44556066d7c54eed6d9c66ac9b268551e026fd120eab52e1bf98b6fc1
Tx public key: e9e9a46e96735f7a4bba8195ec20b1e43d384a7c4e4b316e0c4d51376e0aa199
Timestamp: 1709478681 Timestamp [UCT]: 2024-03-03 15:11:21 Age [y:d:h:m:s]: 01:274:15:43:42
Block: 970333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455054 RingCT/type: yes/0
Extra: 01e9e9a46e96735f7a4bba8195ec20b1e43d384a7c4e4b316e0c4d51376e0aa19902110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb70fbecbb598cd02c68edbe782cde2f96b6bb7add0c4df5833e374bd53ff4fd 0.600000000000 1430184 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": 970343, "vin": [ { "gen": { "height": 970333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb70fbecbb598cd02c68edbe782cde2f96b6bb7add0c4df5833e374bd53ff4fd" } } ], "extra": [ 1, 233, 233, 164, 110, 150, 115, 95, 122, 75, 186, 129, 149, 236, 32, 177, 228, 61, 56, 74, 124, 78, 75, 49, 110, 12, 77, 81, 55, 110, 10, 161, 153, 2, 17, 0, 0, 0, 11, 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