Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ccd7069d63daabd7ebc56b701e667dfc6eb91c66b03c43b22d514ad8750561e

Tx prefix hash: a6ca1ae932310d50aec03fc959d312bdb6ee9b2648fd8fd66194ea08263c01cf
Tx public key: f9fd21759665ae7d7a69ea29004f1be0ee3ba4f55b1e04209ba9a93736386fef
Timestamp: 1707598896 Timestamp [UCT]: 2024-02-10 21:01:36 Age [y:d:h:m:s]: 01:044:13:19:02
Block: 954738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292872 RingCT/type: yes/0
Extra: 01f9fd21759665ae7d7a69ea29004f1be0ee3ba4f55b1e04209ba9a93736386fef02110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96c13df2bdbeebe6ec62a5b8488e321cff561e1002a468bebf571d17b53c1230 0.600000000000 1414020 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": 954748, "vin": [ { "gen": { "height": 954738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96c13df2bdbeebe6ec62a5b8488e321cff561e1002a468bebf571d17b53c1230" } } ], "extra": [ 1, 249, 253, 33, 117, 150, 101, 174, 125, 122, 105, 234, 41, 0, 79, 27, 224, 238, 59, 164, 245, 91, 30, 4, 32, 155, 169, 169, 55, 54, 56, 111, 239, 2, 17, 0, 0, 0, 15, 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