Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c13f4ab46641ddf09cbaf5dc23712dd81e60b3cc431815e627302963b7691e39

Tx prefix hash: 4eaa0bfd2186372c8631c2c47dbcf4f6f5276b29abab8777ba3360e1034d9642
Tx public key: d704bbc5a215c880a7cbbe97e4ac6e230b5eff6c39235cda948c7337816f61f5
Timestamp: 1708157828 Timestamp [UCT]: 2024-02-17 08:17:08 Age [y:d:h:m:s]: 01:038:06:33:56
Block: 959371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288369 RingCT/type: yes/0
Extra: 01d704bbc5a215c880a7cbbe97e4ac6e230b5eff6c39235cda948c7337816f61f502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2bfbeaa01919b1d963d78125ed1b3e490722f2b9ee9300e0aa93ae0eb6af564 0.600000000000 1418906 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": 959381, "vin": [ { "gen": { "height": 959371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2bfbeaa01919b1d963d78125ed1b3e490722f2b9ee9300e0aa93ae0eb6af564" } } ], "extra": [ 1, 215, 4, 187, 197, 162, 21, 200, 128, 167, 203, 190, 151, 228, 172, 110, 35, 11, 94, 255, 108, 57, 35, 92, 218, 148, 140, 115, 55, 129, 111, 97, 245, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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