Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64b090987fd5b1c5aed8cfa6d2b425f56a2a3bda11c656e5e4637ef21082a85

Tx prefix hash: ca17f77c7279fed70fee35ec52aaca0a83f3fc2f4fca5c936af082655285648f
Tx public key: 0c9851b5d5ef2c80fe5b3469ef9673e4bee9475c05aaf21e032a209058e8ba46
Timestamp: 1713214471 Timestamp [UCT]: 2024-04-15 20:54:31 Age [y:d:h:m:s]: 01:199:02:51:12
Block: 1001279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400985 RingCT/type: yes/0
Extra: 010c9851b5d5ef2c80fe5b3469ef9673e4bee9475c05aaf21e032a209058e8ba460211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79154d482fd506918508b5d138b13b0fdd5ff448a776e95cc1077251544639f 0.600000000000 1461783 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": 1001289, "vin": [ { "gen": { "height": 1001279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79154d482fd506918508b5d138b13b0fdd5ff448a776e95cc1077251544639f" } } ], "extra": [ 1, 12, 152, 81, 181, 213, 239, 44, 128, 254, 91, 52, 105, 239, 150, 115, 228, 190, 233, 71, 92, 5, 170, 242, 30, 3, 42, 32, 144, 88, 232, 186, 70, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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