Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50b61a1b9aaae90f31714d2bd946aba5bdf91ec7a2e67d1fca72b21305b773d

Tx prefix hash: 3ba6787470f95944ea719d3657456c3819de5e671c30d75cb182b3d4eb2d56bc
Tx public key: 8d3fe3363ba090cf6b7a0158edaf898e9b56a3a6ed39511551289c9ebf261b9d
Timestamp: 1719252945 Timestamp [UCT]: 2024-06-24 18:15:45 Age [y:d:h:m:s]: 01:160:06:55:32
Block: 1051349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373143 RingCT/type: yes/0
Extra: 018d3fe3363ba090cf6b7a0158edaf898e9b56a3a6ed39511551289c9ebf261b9d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2888c2305731511584243f8d8f2941768553bcd8eb42912e9d65e7edca038a 0.600000000000 1521660 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": 1051359, "vin": [ { "gen": { "height": 1051349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2888c2305731511584243f8d8f2941768553bcd8eb42912e9d65e7edca038a" } } ], "extra": [ 1, 141, 63, 227, 54, 59, 160, 144, 207, 107, 122, 1, 88, 237, 175, 137, 142, 155, 86, 163, 166, 237, 57, 81, 21, 81, 40, 156, 158, 191, 38, 27, 157, 2, 17, 0, 0, 0, 2, 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