Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46ca172e5bf92a3ec2f79a85cbbbb714178e318fe92a6a707e2bc0e0c8a4c7e0

Tx prefix hash: e0d2cf3fa2013498c50f5e6d78ed6e697d4930dd13fcd0e56e12cdec9f08a1b7
Tx public key: 09517ad15c884b2f5a96edd010efa7b90af56d5df4c0e098709920051ba69608
Timestamp: 1713695294 Timestamp [UCT]: 2024-04-21 10:28:14 Age [y:d:h:m:s]: 00:203:19:20:33
Block: 1005285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145890 RingCT/type: yes/0
Extra: 0109517ad15c884b2f5a96edd010efa7b90af56d5df4c0e098709920051ba696080211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 180c24d6a40cd21e9316fe2d6c8a77f22c21a2886d74d59a8d2752c5c6080679 0.600000000000 1465871 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": 1005295, "vin": [ { "gen": { "height": 1005285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "180c24d6a40cd21e9316fe2d6c8a77f22c21a2886d74d59a8d2752c5c6080679" } } ], "extra": [ 1, 9, 81, 122, 209, 92, 136, 75, 47, 90, 150, 237, 208, 16, 239, 167, 185, 10, 245, 109, 93, 244, 192, 224, 152, 112, 153, 32, 5, 27, 166, 150, 8, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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