Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245f61d797ce25800e9e78d392ea1b0941773d20f5c0a3614ce2c75b11b741d3

Tx prefix hash: 383e4bd6a8fe4a290111529edea7567febaea62a5a48779b833af31af58b32be
Tx public key: b8d2af20a3d4b970b9383739ca10f74c878c3e836df0fd8c259173b4b4486af1
Timestamp: 1718745921 Timestamp [UCT]: 2024-06-18 21:25:21 Age [y:d:h:m:s]: 00:279:19:55:56
Block: 1047158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199958 RingCT/type: yes/0
Extra: 01b8d2af20a3d4b970b9383739ca10f74c878c3e836df0fd8c259173b4b4486af102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3047f386e4d4ddcc170e9baf961a9ba20af022b9c0248ed98bb5ebfc011c114 0.600000000000 1516977 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": 1047168, "vin": [ { "gen": { "height": 1047158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3047f386e4d4ddcc170e9baf961a9ba20af022b9c0248ed98bb5ebfc011c114" } } ], "extra": [ 1, 184, 210, 175, 32, 163, 212, 185, 112, 185, 56, 55, 57, 202, 16, 247, 76, 135, 140, 62, 131, 109, 240, 253, 140, 37, 145, 115, 180, 180, 72, 106, 241, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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