Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc2d1ca493d26f9065d01a8dad064eaeb598d19df37f1ea59dfddea8faf8977

Tx prefix hash: 5ac04ab7b3c3824fb6c22a44e75887e2ead1c2b77fc9dc8ff85984437c5e406c
Tx public key: fefca0d7c9e0e95bbc8f0d0f13bfc52f33e8b2678de71199cf7387c4a8830e61
Timestamp: 1723246681 Timestamp [UCT]: 2024-08-09 23:38:01 Age [y:d:h:m:s]: 00:240:13:43:17
Block: 1084471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171816 RingCT/type: yes/0
Extra: 01fefca0d7c9e0e95bbc8f0d0f13bfc52f33e8b2678de71199cf7387c4a8830e6102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 610cffaf0f2a07b60acfe6c3e601a9e5b851b6b17ce5747105f00064da723ca0 0.600000000000 1558760 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": 1084481, "vin": [ { "gen": { "height": 1084471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "610cffaf0f2a07b60acfe6c3e601a9e5b851b6b17ce5747105f00064da723ca0" } } ], "extra": [ 1, 254, 252, 160, 215, 201, 224, 233, 91, 188, 143, 13, 15, 19, 191, 197, 47, 51, 232, 178, 103, 141, 231, 17, 153, 207, 115, 135, 196, 168, 131, 14, 97, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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