Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46be6db079098f6bd472c20243daf126b002d28b2bbc979a6356ad24a0c8236

Tx prefix hash: d408aa859877087e042d2c99040f9811700002ab1349f73c9a31426c02e0e8ac
Tx public key: 9b5d5f2db3e5cfc4dce55281f65c89e75bbdb04023ceb058e1d65effa7e7297f
Timestamp: 1749226172 Timestamp [UCT]: 2025-06-06 16:09:32 Age [y:d:h:m:s]: 00:167:06:18:27
Block: 1299305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117225 RingCT/type: yes/0
Extra: 019b5d5f2db3e5cfc4dce55281f65c89e75bbdb04023ceb058e1d65effa7e7297f02110000000f43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d9b7374538c3caa73bd86e1ad58ff8dbcbc806e0e0d3b18d83790aa2feca21a 0.600000000000 1786842 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": 1299315, "vin": [ { "gen": { "height": 1299305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d9b7374538c3caa73bd86e1ad58ff8dbcbc806e0e0d3b18d83790aa2feca21a" } } ], "extra": [ 1, 155, 93, 95, 45, 179, 229, 207, 196, 220, 229, 82, 129, 246, 92, 137, 231, 91, 189, 176, 64, 35, 206, 176, 88, 225, 214, 94, 255, 167, 231, 41, 127, 2, 17, 0, 0, 0, 15, 67, 132, 109, 102, 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