Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487b921b6da9239a2c131b1aa035df483e29584782cd55a0ae471c6e37ef36ee

Tx prefix hash: e9c5edec7dd4b1b6598d36e7864e7f38b964b6cbf6123be071c9542050b01513
Tx public key: 68cce304590e3786514ed8f335650fb7fe60a5e9cf6de7ccb06b52f730530c4f
Timestamp: 1718054971 Timestamp [UCT]: 2024-06-10 21:29:31 Age [y:d:h:m:s]: 00:354:05:37:27
Block: 1041431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253195 RingCT/type: yes/0
Extra: 0168cce304590e3786514ed8f335650fb7fe60a5e9cf6de7ccb06b52f730530c4f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48a6bc2a9915900b7b1cc3e4fca558da665d49a79d2a4159c3817d7a79be0403 0.600000000000 1510104 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": 1041441, "vin": [ { "gen": { "height": 1041431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48a6bc2a9915900b7b1cc3e4fca558da665d49a79d2a4159c3817d7a79be0403" } } ], "extra": [ 1, 104, 204, 227, 4, 89, 14, 55, 134, 81, 78, 216, 243, 53, 101, 15, 183, 254, 96, 165, 233, 207, 109, 231, 204, 176, 107, 82, 247, 48, 83, 12, 79, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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