Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3952ad4319185aff1b556ab0eb803ad283f5a16e9d67e83ffae1df6244d4434

Tx prefix hash: 0e5fdade296da246bf83f5c9e69db6c85092dcca7d364285fbb01f0a411b6634
Tx public key: 882d7307d59b566049a970514d49c9bbcfbebd6cc74fd315b42ce5be3feb4e23
Timestamp: 1710795028 Timestamp [UCT]: 2024-03-18 20:50:28 Age [y:d:h:m:s]: 01:236:16:50:19
Block: 981261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427849 RingCT/type: yes/0
Extra: 01882d7307d59b566049a970514d49c9bbcfbebd6cc74fd315b42ce5be3feb4e2302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf1bbfba87e6dce4509c6fc0c55eec224fe06e55db054b9b95be3b44a2400a3d 0.600000000000 1441356 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": 981271, "vin": [ { "gen": { "height": 981261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf1bbfba87e6dce4509c6fc0c55eec224fe06e55db054b9b95be3b44a2400a3d" } } ], "extra": [ 1, 136, 45, 115, 7, 213, 155, 86, 96, 73, 169, 112, 81, 77, 73, 201, 187, 207, 190, 189, 108, 199, 79, 211, 21, 180, 44, 229, 190, 63, 235, 78, 35, 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