Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad875c88044ca53fd8a98222c5d146e8d36c728c343851f2b2b8d4f054e416ed

Tx prefix hash: 565060b9031eee8dd4345d5b09547cef086eaf69d22d94a0957399526a8ea7dd
Tx public key: 230309c574730b16b5558927f0a4300877d17ce410d5df6bc6eda566fa8ed1b6
Timestamp: 1694934253 Timestamp [UCT]: 2023-09-17 07:04:13 Age [y:d:h:m:s]: 01:180:08:59:00
Block: 849934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390014 RingCT/type: yes/0
Extra: 01230309c574730b16b5558927f0a4300877d17ce410d5df6bc6eda566fa8ed1b602110000000533af99f4000000000000000000

1 output(s) for total of 0.937164632000 dcy

stealth address amount amount idx
00: 6806d93ec8c694880040361ef317764e205c61b89d139b058642e5a29d3aa47f 0.937164632000 1303624 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": 849944, "vin": [ { "gen": { "height": 849934 } } ], "vout": [ { "amount": 937164632, "target": { "key": "6806d93ec8c694880040361ef317764e205c61b89d139b058642e5a29d3aa47f" } } ], "extra": [ 1, 35, 3, 9, 197, 116, 115, 11, 22, 181, 85, 137, 39, 240, 164, 48, 8, 119, 209, 124, 228, 16, 213, 223, 107, 198, 237, 165, 102, 250, 142, 209, 182, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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