Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a866662300d0f64b949f08be3316afce908470278058b2f0bb38f61b7f05075

Tx prefix hash: 5d4ffb6671e289a9ccd3c575e0e3363a31bd80a6c8a5395f7adf04bf96de1a7c
Tx public key: dbcb10ac21a6f1d9259183f5b2dcabc830e325017513b6e60cd0e333c90ec37b
Timestamp: 1706804376 Timestamp [UCT]: 2024-02-01 16:19:36 Age [y:d:h:m:s]: 01:076:22:11:45
Block: 948140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316065 RingCT/type: yes/0
Extra: 01dbcb10ac21a6f1d9259183f5b2dcabc830e325017513b6e60cd0e333c90ec37b02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a5f9162a8930ad556fbc2c72acc730e3216fd71767d3dcbba592acdebf0255 0.600000000000 1406512 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": 948150, "vin": [ { "gen": { "height": 948140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a5f9162a8930ad556fbc2c72acc730e3216fd71767d3dcbba592acdebf0255" } } ], "extra": [ 1, 219, 203, 16, 172, 33, 166, 241, 217, 37, 145, 131, 245, 178, 220, 171, 200, 48, 227, 37, 1, 117, 19, 182, 230, 12, 208, 227, 51, 201, 14, 195, 123, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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