Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8153a4d38c8abc1388713c2f99c5127a68b5a30e58ef2123b9f84d1b80baab2b

Tx prefix hash: 01518dc521d8f3039228d517bbb62fbdcca7a5ec558ab9dd81fc9eb173c15492
Tx public key: 0163adf058b9afd23f68ac8c02b47ff2dfd8e1c173038d5fc288be3c3cb45016
Timestamp: 1700823937 Timestamp [UCT]: 2023-11-24 11:05:37 Age [y:d:h:m:s]: 01:133:21:37:18
Block: 898565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356876 RingCT/type: yes/0
Extra: 010163adf058b9afd23f68ac8c02b47ff2dfd8e1c173038d5fc288be3c3cb45016021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.646667639000 dcy

stealth address amount amount idx
00: d414b516e2b1086c9af9a313de2186f12fdbe3eb71eee00163b0e4d9b22f2036 0.646667639000 1354986 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": 898575, "vin": [ { "gen": { "height": 898565 } } ], "vout": [ { "amount": 646667639, "target": { "key": "d414b516e2b1086c9af9a313de2186f12fdbe3eb71eee00163b0e4d9b22f2036" } } ], "extra": [ 1, 1, 99, 173, 240, 88, 185, 175, 210, 63, 104, 172, 140, 2, 180, 127, 242, 223, 216, 225, 193, 115, 3, 141, 95, 194, 136, 190, 60, 60, 180, 80, 22, 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