Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476ac5763850d3f37ca9512e680b263e217f7e1c3360ec97aa74311ef4281e29

Tx prefix hash: 7af9e46db68958b3899e6073ebf189ced3c05d6986dc3f491958b3c6d28f74ba
Tx public key: 62372c225bf4f2a23338f9fb7c9d0c9b1a29f67a65803dc5320281d50c5bf748
Timestamp: 1723145565 Timestamp [UCT]: 2024-08-08 19:32:45 Age [y:d:h:m:s]: 00:198:14:55:56
Block: 1083629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141811 RingCT/type: yes/0
Extra: 0162372c225bf4f2a23338f9fb7c9d0c9b1a29f67a65803dc5320281d50c5bf74802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3633da8b6309d92ae8618996a272cce202384a0fe90309d71c18bf48c57e4e9a 0.600000000000 1557618 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": 1083639, "vin": [ { "gen": { "height": 1083629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3633da8b6309d92ae8618996a272cce202384a0fe90309d71c18bf48c57e4e9a" } } ], "extra": [ 1, 98, 55, 44, 34, 91, 244, 242, 162, 51, 56, 249, 251, 124, 157, 12, 155, 26, 41, 246, 122, 101, 128, 61, 197, 50, 2, 129, 213, 12, 91, 247, 72, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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