Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a52adf3827e6037d387e7124293aeb8811d79c298e2d67a2a48de0e4cf3afbc

Tx prefix hash: f7a2730c72d1254710dd203d41b0b77d8f67a38fec0b40bfec027fb3b3a5e270
Tx public key: 8507e72678e2d7a26d234fa0a11e0705732b623754b3396349ea9a2fb5387d55
Timestamp: 1741389130 Timestamp [UCT]: 2025-03-07 23:12:10 Age [y:d:h:m:s]: 00:258:22:05:04
Block: 1234420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182794 RingCT/type: yes/0
Extra: 018507e72678e2d7a26d234fa0a11e0705732b623754b3396349ea9a2fb5387d550211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14bedea59e0672c8770a734ff42554c7c761b4400c5e7c77a11499d4107f53f4 0.600000000000 1721347 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": 1234430, "vin": [ { "gen": { "height": 1234420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14bedea59e0672c8770a734ff42554c7c761b4400c5e7c77a11499d4107f53f4" } } ], "extra": [ 1, 133, 7, 231, 38, 120, 226, 215, 162, 109, 35, 79, 160, 161, 30, 7, 5, 115, 43, 98, 55, 84, 179, 57, 99, 73, 234, 154, 47, 181, 56, 125, 85, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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