Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe618bb11f51a976c2b38376d159636dde49d86acd970d9d212d4b5bab4c2a7

Tx prefix hash: ad379e120fe669eade0bdd1dfe89ec3f4105ccaa417a3eb918c556e7ce33f445
Tx public key: d6762d0d754f0dba681186dca39636c9901b2d5a896614bb3e2923a25639addd
Timestamp: 1696707701 Timestamp [UCT]: 2023-10-07 19:41:41 Age [y:d:h:m:s]: 01:253:23:38:16
Block: 864653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442496 RingCT/type: yes/0
Extra: 01d6762d0d754f0dba681186dca39636c9901b2d5a896614bb3e2923a25639addd021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.837617441000 dcy

stealth address amount amount idx
00: e13129fd960eb548e0bf4be20b40c3d063b37e8754ac0d826fbe051d10e536a3 0.837617441000 1319173 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": 864663, "vin": [ { "gen": { "height": 864653 } } ], "vout": [ { "amount": 837617441, "target": { "key": "e13129fd960eb548e0bf4be20b40c3d063b37e8754ac0d826fbe051d10e536a3" } } ], "extra": [ 1, 214, 118, 45, 13, 117, 79, 13, 186, 104, 17, 134, 220, 163, 150, 54, 201, 144, 27, 45, 90, 137, 102, 20, 187, 62, 41, 35, 162, 86, 57, 173, 221, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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