Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85709a984d48b940b8d4ad7ddd9537e008ab218d028d2264f70ca58cdfe09321

Tx prefix hash: 7d95f3b2108f6c31275e9c5ccbecad33410075214df7f05dc79b5c9ec0b06f3a
Tx public key: 076bcf279f177dd647b466ae1df69f0bd2ee58a7a79bf0792b6d0b7a36064b71
Timestamp: 1745632587 Timestamp [UCT]: 2025-04-26 01:56:27 Age [y:d:h:m:s]: 00:209:07:15:33
Block: 1269534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147308 RingCT/type: yes/0
Extra: 01076bcf279f177dd647b466ae1df69f0bd2ee58a7a79bf0792b6d0b7a36064b710211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f179e5e9a8a8027af8773600bf5aa67a249b8cd13f91de172d81f0313ee9fb60 0.600000000000 1756773 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": 1269544, "vin": [ { "gen": { "height": 1269534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f179e5e9a8a8027af8773600bf5aa67a249b8cd13f91de172d81f0313ee9fb60" } } ], "extra": [ 1, 7, 107, 207, 39, 159, 23, 125, 214, 71, 180, 102, 174, 29, 246, 159, 11, 210, 238, 88, 167, 167, 155, 240, 121, 43, 109, 11, 122, 54, 6, 75, 113, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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