Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31242b28b52022016724119bf171049740b3ee9cbcee5fdfc5bed03b85cbef80

Tx prefix hash: c3a9b78f2076104a3ca1dd06a75d6299c1ecf72b70c110294b0d07d3d0e5fa69
Tx public key: fa9c18120422697946f6e62f6fa6da2605c763b6c1fff32c7ddc1d0e75d577fc
Timestamp: 1740941200 Timestamp [UCT]: 2025-03-02 18:46:40 Age [y:d:h:m:s]: 00:263:03:41:19
Block: 1230708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185822 RingCT/type: yes/0
Extra: 01fa9c18120422697946f6e62f6fa6da2605c763b6c1fff32c7ddc1d0e75d577fc02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0231f3efca64f4da23f47c993cb240651c751e5d5338bbf8dad69f298d08970d 0.600000000000 1717607 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": 1230718, "vin": [ { "gen": { "height": 1230708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0231f3efca64f4da23f47c993cb240651c751e5d5338bbf8dad69f298d08970d" } } ], "extra": [ 1, 250, 156, 24, 18, 4, 34, 105, 121, 70, 246, 230, 47, 111, 166, 218, 38, 5, 199, 99, 182, 193, 255, 243, 44, 125, 220, 29, 14, 117, 213, 119, 252, 2, 17, 0, 0, 0, 12, 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