Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9e85b4f4ea2a6b1d8b227f87e0771605e9cf7a0ee000ca4d53721e90ada5a8

Tx prefix hash: 2f38164c73ed02933c6bb1b6460b5b950200e07ac10b6c2e6fbac988afeaa53e
Tx public key: 0b82f918c0f159eb3da55f59d5bd75d06ca8f9ef2819700627b61ae8abc2d88d
Timestamp: 1684854554 Timestamp [UCT]: 2023-05-23 15:09:14 Age [y:d:h:m:s]: 01:321:16:49:59
Block: 766441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491120 RingCT/type: yes/0
Extra: 010b82f918c0f159eb3da55f59d5bd75d06ca8f9ef2819700627b61ae8abc2d88d021100000001faf35c9c000000000000000000

1 output(s) for total of 1.771996996000 dcy

stealth address amount amount idx
00: aef6954223681dce1d2c7360ab4f7d1e3bb67fe4583e23e49d3a547e4c201cb7 1.771996996000 1215482 of 0

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": 766451, "vin": [ { "gen": { "height": 766441 } } ], "vout": [ { "amount": 1771996996, "target": { "key": "aef6954223681dce1d2c7360ab4f7d1e3bb67fe4583e23e49d3a547e4c201cb7" } } ], "extra": [ 1, 11, 130, 249, 24, 192, 241, 89, 235, 61, 165, 95, 89, 213, 189, 117, 208, 108, 168, 249, 239, 40, 25, 112, 6, 39, 182, 26, 232, 171, 194, 216, 141, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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