Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5100de15d4cdafc1a44a88ee9ed99c10b7eb441631668c5d23bfcb68a93509

Tx prefix hash: 241f3979ffe4b55f22f7a3e0493088cc3ed51fe58bbf25e2e72b5ffe482b8c1a
Tx public key: 92e92c4affd3c14e22e1a41e075ffa839e174003036a65bcecf2a3d5856c1d4d
Timestamp: 1734735960 Timestamp [UCT]: 2024-12-20 23:06:00 Age [y:d:h:m:s]: 00:134:00:42:32
Block: 1179639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95562 RingCT/type: yes/0
Extra: 0192e92c4affd3c14e22e1a41e075ffa839e174003036a65bcecf2a3d5856c1d4d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7fe1b0823d5bb799ec819ad087b2e7b64a254fb8bf55ea9d35b0176dc90e37b 0.600000000000 1666038 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": 1179649, "vin": [ { "gen": { "height": 1179639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7fe1b0823d5bb799ec819ad087b2e7b64a254fb8bf55ea9d35b0176dc90e37b" } } ], "extra": [ 1, 146, 233, 44, 74, 255, 211, 193, 78, 34, 225, 164, 30, 7, 95, 250, 131, 158, 23, 64, 3, 3, 106, 101, 188, 236, 242, 163, 213, 133, 108, 29, 77, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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