Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477a89f5fe795b03ac0e08008903b75619e7c4b66783065d41b7a9bcf0b0bcc8

Tx prefix hash: 8ffcadef900927f88d61a3dcfd7b312459c7615ada204b47b5cf3a7e7ca0b390
Tx public key: 37e724ce7b63e903e10ea64cb54079180c3b7787185111def8c43349bb4da1d0
Timestamp: 1737855888 Timestamp [UCT]: 2025-01-26 01:44:48 Age [y:d:h:m:s]: 00:142:07:37:12
Block: 1205392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101462 RingCT/type: yes/0
Extra: 0137e724ce7b63e903e10ea64cb54079180c3b7787185111def8c43349bb4da1d00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9419e783d36c18bb9b4d82dee0ae4431ea4e3313d109795ba52d397f1b384d46 0.600000000000 1692089 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": 1205402, "vin": [ { "gen": { "height": 1205392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9419e783d36c18bb9b4d82dee0ae4431ea4e3313d109795ba52d397f1b384d46" } } ], "extra": [ 1, 55, 231, 36, 206, 123, 99, 233, 3, 225, 14, 166, 76, 181, 64, 121, 24, 12, 59, 119, 135, 24, 81, 17, 222, 248, 196, 51, 73, 187, 77, 161, 208, 2, 17, 0, 0, 0, 3, 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