Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2305773e01a86b3a41cb02f06f7baff4b597d26f15d48b8f4ee708f46693b2db

Tx prefix hash: a7a54c566e946e09ad9ec4307e661221e32e86f181363ffbeab930a255dcbfeb
Tx public key: c5c0d9314c4732a0a99b4505f6752e69fa807c0d115dacbb547261d40112c40c
Timestamp: 1696182025 Timestamp [UCT]: 2023-10-01 17:40:25 Age [y:d:h:m:s]: 01:263:15:48:15
Block: 860296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449358 RingCT/type: yes/0
Extra: 01c5c0d9314c4732a0a99b4505f6752e69fa807c0d115dacbb547261d40112c40c0211000000054b8f5122000000000000000000

1 output(s) for total of 0.865928967000 dcy

stealth address amount amount idx
00: e4882debdff5bc77bcf0586b885da59963eb2141f1f4173cb97621abadbe9e0d 0.865928967000 1314572 of 0

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": 860306, "vin": [ { "gen": { "height": 860296 } } ], "vout": [ { "amount": 865928967, "target": { "key": "e4882debdff5bc77bcf0586b885da59963eb2141f1f4173cb97621abadbe9e0d" } } ], "extra": [ 1, 197, 192, 217, 49, 76, 71, 50, 160, 169, 155, 69, 5, 246, 117, 46, 105, 250, 128, 124, 13, 17, 93, 172, 187, 84, 114, 97, 212, 1, 18, 196, 12, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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