Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91556d73dc4ba9063faf3fcfd636166f7aeff60792c0e649c1f0573ac1a3348f

Tx prefix hash: 98532e805327269e34bd6ad44a503530c585a74cdbbb7a6c5b0ac093f4a54ac3
Tx public key: 276c825b2387fcc387d04081560eaaf711c6bfde4a89a35b964c318c57e40b13
Timestamp: 1735017089 Timestamp [UCT]: 2024-12-24 05:11:29 Age [y:d:h:m:s]: 00:098:07:19:29
Block: 1181940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70030 RingCT/type: yes/0
Extra: 01276c825b2387fcc387d04081560eaaf711c6bfde4a89a35b964c318c57e40b130211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcfb768ab71f64a9d23f8fd9ff458bd5bf22030fd392ae3f114ff51b408f6dd0 0.600000000000 1668369 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": 1181950, "vin": [ { "gen": { "height": 1181940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcfb768ab71f64a9d23f8fd9ff458bd5bf22030fd392ae3f114ff51b408f6dd0" } } ], "extra": [ 1, 39, 108, 130, 91, 35, 135, 252, 195, 135, 208, 64, 129, 86, 14, 170, 247, 17, 198, 191, 222, 74, 137, 163, 91, 150, 76, 49, 140, 87, 228, 11, 19, 2, 17, 0, 0, 0, 3, 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