Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f3a1315a0673f6b6a3f4b86f91f676bcc952abaa4657d77eaa1bfccd8108a5

Tx prefix hash: a5493334a93424b072018c1318913cdb1aa4a126fe3bd4bc4633c6fac1e41297
Tx public key: d3accafe26ef9f8e4b90b4cf1eb19179314c634cb27ae57c5c9f69bf808f7e27
Timestamp: 1731373576 Timestamp [UCT]: 2024-11-12 01:06:16 Age [y:d:h:m:s]: 00:147:21:15:05
Block: 1151753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105517 RingCT/type: yes/0
Extra: 01d3accafe26ef9f8e4b90b4cf1eb19179314c634cb27ae57c5c9f69bf808f7e27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1005496ce04907dea28017d1ad053ffe08b414bc4e30008de1e2335db4a7cb64 0.600000000000 1637336 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": 1151763, "vin": [ { "gen": { "height": 1151753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1005496ce04907dea28017d1ad053ffe08b414bc4e30008de1e2335db4a7cb64" } } ], "extra": [ 1, 211, 172, 202, 254, 38, 239, 159, 142, 75, 144, 180, 207, 30, 177, 145, 121, 49, 76, 99, 76, 178, 122, 229, 124, 92, 159, 105, 191, 128, 143, 126, 39, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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