Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6f8d52ddcaa22e74347472e5ec6cd931d5dfa3a49c7b984cba92cdb05038eb

Tx prefix hash: d81c6a7064de940c7ccbb7da477dbce790092c7c77dd451ce199f616120a213c
Tx public key: 13b186cecba138b27258eee502d2a78975553429dc252476a7baf4d7f65c9f69
Timestamp: 1703033883 Timestamp [UCT]: 2023-12-20 00:58:03 Age [y:d:h:m:s]: 01:108:11:03:51
Block: 916903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338632 RingCT/type: yes/0
Extra: 0113b186cecba138b27258eee502d2a78975553429dc252476a7baf4d7f65c9f6902110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ff586e5628c10d53a6a203ccc0c486e28f9ef49fb210018f04ee946874d3cd5 0.600000000000 1374465 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": 916913, "vin": [ { "gen": { "height": 916903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ff586e5628c10d53a6a203ccc0c486e28f9ef49fb210018f04ee946874d3cd5" } } ], "extra": [ 1, 19, 177, 134, 206, 203, 161, 56, 178, 114, 88, 238, 229, 2, 210, 167, 137, 117, 85, 52, 41, 220, 37, 36, 118, 167, 186, 244, 215, 246, 92, 159, 105, 2, 17, 0, 0, 0, 12, 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