Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78499411d4d97548c045f505d1c47fa76c00d445e2c466d924ffcdc2c4f834d3

Tx prefix hash: 0bdde2716f98d04b585a0a0edcc3e54323f7e9556d480ca05a55eac94495a617
Tx public key: 515974965bed3b9c43c76e7991645f6cbdd7f91986f6d7cfba76aabf4f9fe38b
Timestamp: 1745839320 Timestamp [UCT]: 2025-04-28 11:22:00 Age [y:d:h:m:s]: 00:014:16:24:45
Block: 1271264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10493 RingCT/type: yes/0
Extra: 01515974965bed3b9c43c76e7991645f6cbdd7f91986f6d7cfba76aabf4f9fe38b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f80ba8e70ed0d093a9191e35ff13a9caa6afc53c75580f638eef994fbdecb8dc 0.600000000000 1758521 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": 1271274, "vin": [ { "gen": { "height": 1271264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f80ba8e70ed0d093a9191e35ff13a9caa6afc53c75580f638eef994fbdecb8dc" } } ], "extra": [ 1, 81, 89, 116, 150, 91, 237, 59, 156, 67, 199, 110, 121, 145, 100, 95, 108, 189, 215, 249, 25, 134, 246, 215, 207, 186, 118, 170, 191, 79, 159, 227, 139, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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