Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11fcec617a7dc29f426b571833679bb437e6c2fd23625d724978d27bc80bb0b

Tx prefix hash: b0e0eaf3735682455b02788795af82b8e3a8c9404e1853fd20d54aca191dbbb9
Tx public key: 097af58b19351f97dd5c4ecb68ff43d3048ce088b2655de6c8e6a78d583d435d
Timestamp: 1704375149 Timestamp [UCT]: 2024-01-04 13:32:29 Age [y:d:h:m:s]: 01:095:22:17:03
Block: 928028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329660 RingCT/type: yes/0
Extra: 01097af58b19351f97dd5c4ecb68ff43d3048ce088b2655de6c8e6a78d583d435d021100000007679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 723c9dcab625e3cd6678eb6ee5899eca9a70da002d7f5d17fc2d6378067c60b0 0.600000000000 1385884 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": 928038, "vin": [ { "gen": { "height": 928028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "723c9dcab625e3cd6678eb6ee5899eca9a70da002d7f5d17fc2d6378067c60b0" } } ], "extra": [ 1, 9, 122, 245, 139, 25, 53, 31, 151, 221, 92, 78, 203, 104, 255, 67, 211, 4, 140, 224, 136, 178, 101, 93, 230, 200, 230, 167, 141, 88, 61, 67, 93, 2, 17, 0, 0, 0, 7, 103, 154, 138, 129, 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