Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 142b7d4859cd7dbc49ba3fa852546b9f61af35501f81463658de0263888fd64d

Tx prefix hash: 1c2151ddf3cabcccd5cf49649fc25b506ad481cb565a5059d88801e7113b433c
Tx public key: e9bf87a1c862a28d9e18006f62cac1bc94e91081bb60d401c761a3bbf2bb8929
Timestamp: 1685096083 Timestamp [UCT]: 2023-05-26 10:14:43 Age [y:d:h:m:s]: 02:166:01:54:42
Block: 768434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638486 RingCT/type: yes/0
Extra: 01e9bf87a1c862a28d9e18006f62cac1bc94e91081bb60d401c761a3bbf2bb8929021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.745256813000 dcy

stealth address amount amount idx
00: f0b7dcae72c4c4b3deead7097b349ea8305d9717f56524d97f4cc0b0a5bfc749 1.745256813000 1217631 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": 768444, "vin": [ { "gen": { "height": 768434 } } ], "vout": [ { "amount": 1745256813, "target": { "key": "f0b7dcae72c4c4b3deead7097b349ea8305d9717f56524d97f4cc0b0a5bfc749" } } ], "extra": [ 1, 233, 191, 135, 161, 200, 98, 162, 141, 158, 24, 0, 111, 98, 202, 193, 188, 148, 233, 16, 129, 187, 96, 212, 1, 199, 97, 163, 187, 242, 187, 137, 41, 2, 17, 0, 0, 0, 2, 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