Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222ccdc226b6e1a336b7036376dcfdfd592dfb445ff1d06ed407e05ca97bb1d0

Tx prefix hash: 56636ee54dd7e00550d402a757980527db1c815786e12fa4bb69ab601b2e4c2b
Tx public key: abca5869371eae240ac852e2f3d05bc5d8274b5f70c60b8de08c1644d5e0a2ab
Timestamp: 1712591144 Timestamp [UCT]: 2024-04-08 15:45:44 Age [y:d:h:m:s]: 01:068:17:02:53
Block: 996096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310023 RingCT/type: yes/0
Extra: 01abca5869371eae240ac852e2f3d05bc5d8274b5f70c60b8de08c1644d5e0a2ab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2675b0e56ad39456651c13ed92d35c4993ad22523d44463b8c9e07f1e7059866 0.600000000000 1456512 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": 996106, "vin": [ { "gen": { "height": 996096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2675b0e56ad39456651c13ed92d35c4993ad22523d44463b8c9e07f1e7059866" } } ], "extra": [ 1, 171, 202, 88, 105, 55, 30, 174, 36, 10, 200, 82, 226, 243, 208, 91, 197, 216, 39, 75, 95, 112, 198, 11, 141, 224, 140, 22, 68, 213, 224, 162, 171, 2, 17, 0, 0, 0, 1, 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