Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d36a8e7a362df130c27694896875cedcc7a4d49aef0cf2c47ed9d42ae0c9c85

Tx prefix hash: 672a60f3229aced528a28762d2073b5797bd06f8fe91baf626a9e10f280d8aff
Tx public key: 8445053106b01cf1c473e5454ecf8e1c64f419724e636cddd1c16f3a296b31b6
Timestamp: 1703505126 Timestamp [UCT]: 2023-12-25 11:52:06 Age [y:d:h:m:s]: 01:321:06:02:24
Block: 920798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488441 RingCT/type: yes/0
Extra: 018445053106b01cf1c473e5454ecf8e1c64f419724e636cddd1c16f3a296b31b602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94959d0a1cc865e4715dee55a8c34303b84cc03725ebe5b72854aa0b32b70dc9 0.600000000000 1378482 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": 920808, "vin": [ { "gen": { "height": 920798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94959d0a1cc865e4715dee55a8c34303b84cc03725ebe5b72854aa0b32b70dc9" } } ], "extra": [ 1, 132, 69, 5, 49, 6, 176, 28, 241, 196, 115, 229, 69, 78, 207, 142, 28, 100, 244, 25, 114, 78, 99, 108, 221, 209, 193, 111, 58, 41, 107, 49, 182, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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