Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e70d7443a68d361e29be70b81429ae9d8972aa88cdd75110c56270b0069951d

Tx prefix hash: e97b512b0ca8bbcaf7d52b8b87d30d5acea5280742438233d9bc57bbb1a2e7ff
Tx public key: d4fa3ff9a31374ca6ee3a40d06f5684e81539b603a997d019d56ba118f3d48e1
Timestamp: 1723273323 Timestamp [UCT]: 2024-08-10 07:02:03 Age [y:d:h:m:s]: 00:250:22:52:57
Block: 1084697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179247 RingCT/type: yes/0
Extra: 01d4fa3ff9a31374ca6ee3a40d06f5684e81539b603a997d019d56ba118f3d48e1021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e3db2017ed860b0406aa78943d602e530c04fdb3a89c312c52172a9ab124a4 0.600000000000 1559068 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": 1084707, "vin": [ { "gen": { "height": 1084697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e3db2017ed860b0406aa78943d602e530c04fdb3a89c312c52172a9ab124a4" } } ], "extra": [ 1, 212, 250, 63, 249, 163, 19, 116, 202, 110, 227, 164, 13, 6, 245, 104, 78, 129, 83, 155, 96, 58, 153, 125, 1, 157, 86, 186, 17, 143, 61, 72, 225, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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