Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d3aa2af6336dbb7332a7b80adfc83f072c57687f4e3900348aaaf616ce3766e

Tx prefix hash: ee2a46756320660ec70d0c0350b0fe4f896d39f8080632bd335f96c764859a9f
Tx public key: 9bb51cd8a37367713feae5a0a93f0aaf373c5fdaaaf8e488ececed9395b55b5a
Timestamp: 1716970338 Timestamp [UCT]: 2024-05-29 08:12:18 Age [y:d:h:m:s]: 00:343:19:59:27
Block: 1032445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245749 RingCT/type: yes/0
Extra: 019bb51cd8a37367713feae5a0a93f0aaf373c5fdaaaf8e488ececed9395b55b5a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2f8c085117ce3810b2dceb5b9119fd1e1233f84298cb7e6bed63e978b9501fa 0.600000000000 1500898 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": 1032455, "vin": [ { "gen": { "height": 1032445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2f8c085117ce3810b2dceb5b9119fd1e1233f84298cb7e6bed63e978b9501fa" } } ], "extra": [ 1, 155, 181, 28, 216, 163, 115, 103, 113, 63, 234, 229, 160, 169, 63, 10, 175, 55, 60, 95, 218, 170, 248, 228, 136, 236, 236, 237, 147, 149, 181, 91, 90, 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