Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ddd7845aca31eea934295d526d3e260d0e8f6d73a2c55d0ced644ad576e817

Tx prefix hash: 7c558309737ba4f7401e36e28eec37c13c1d9f7170d38a6fd6fa922308bff4af
Tx public key: 8073c5a5eeda5cc5a45b0fac772bb787ae51347cb89a36ecf6ffc6b2757e6ef9
Timestamp: 1741458850 Timestamp [UCT]: 2025-03-08 18:34:10 Age [y:d:h:m:s]: 00:328:03:34:58
Block: 1235009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232167 RingCT/type: yes/0
Extra: 018073c5a5eeda5cc5a45b0fac772bb787ae51347cb89a36ecf6ffc6b2757e6ef90211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 938aabc6612c4d7538eae0d431c7c99158f1703abcf6a3d22c45645183a93e59 0.600000000000 1721944 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": 1235019, "vin": [ { "gen": { "height": 1235009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "938aabc6612c4d7538eae0d431c7c99158f1703abcf6a3d22c45645183a93e59" } } ], "extra": [ 1, 128, 115, 197, 165, 238, 218, 92, 197, 164, 91, 15, 172, 119, 43, 183, 135, 174, 81, 52, 124, 184, 154, 54, 236, 246, 255, 198, 178, 117, 126, 110, 249, 2, 17, 0, 0, 0, 16, 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