Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ccebb18d4ef5169b9c23cbdf5372c71ca2868d46d76d9137d5470d413fca5b

Tx prefix hash: b0d067e3b80817a8f9ae4351feed99ca7233734cf363d125fb2f0fdf06e2d8f2
Tx public key: 11fb75d1f3afed115f41bdfb21c251e569539fab3d30f525cdad51e76d6c3922
Timestamp: 1697456641 Timestamp [UCT]: 2023-10-16 11:44:01 Age [y:d:h:m:s]: 01:218:23:13:39
Block: 870860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417562 RingCT/type: yes/0
Extra: 0111fb75d1f3afed115f41bdfb21c251e569539fab3d30f525cdad51e76d6c392202110000000a33af99f4000000000000000000

1 output(s) for total of 0.798875928000 dcy

stealth address amount amount idx
00: 436a2be56d5044311c6806142d9131877ba947514af5989ac2aaf3e8104ccd06 0.798875928000 1325815 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": 870870, "vin": [ { "gen": { "height": 870860 } } ], "vout": [ { "amount": 798875928, "target": { "key": "436a2be56d5044311c6806142d9131877ba947514af5989ac2aaf3e8104ccd06" } } ], "extra": [ 1, 17, 251, 117, 209, 243, 175, 237, 17, 95, 65, 189, 251, 33, 194, 81, 229, 105, 83, 159, 171, 61, 48, 245, 37, 205, 173, 81, 231, 109, 108, 57, 34, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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