Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5910b5e5a6c3ed74cb7e789c6569f47b8f29563d5758a8d0411049944b2383a2

Tx prefix hash: f0b2222177aed03f42c523af8ecaefaf374b6648896ba7b01df8f801681d310e
Tx public key: 6f7598453b03e353b99a8b9dcbf9884ffc8cb49db05c917bd62a8de3852c019b
Timestamp: 1711316000 Timestamp [UCT]: 2024-03-24 21:33:20 Age [y:d:h:m:s]: 01:015:19:09:20
Block: 985579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272245 RingCT/type: yes/0
Extra: 016f7598453b03e353b99a8b9dcbf9884ffc8cb49db05c917bd62a8de3852c019b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f0b8bc6fc264645986dec8b06a69febc571892d18e2d2deb2d7ddb9963e1f23 0.600000000000 1445796 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": 985589, "vin": [ { "gen": { "height": 985579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f0b8bc6fc264645986dec8b06a69febc571892d18e2d2deb2d7ddb9963e1f23" } } ], "extra": [ 1, 111, 117, 152, 69, 59, 3, 227, 83, 185, 154, 139, 157, 203, 249, 136, 79, 252, 140, 180, 157, 176, 92, 145, 123, 214, 42, 141, 227, 133, 44, 1, 155, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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