Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9575c082f170325d3dbdf8bfb0357cdc7c6784f971caf006b907e8c3660442f7

Tx prefix hash: 63a479ce8bcd16539e03721bc1d18fdf6582ac3355d83445d2dfd63421690aae
Tx public key: 3bed7b40d5039bb2b3b2010d63ca3018bda6540bf66b2c808bbc16899b2f6103
Timestamp: 1721226863 Timestamp [UCT]: 2024-07-17 14:34:23 Age [y:d:h:m:s]: 00:254:09:40:20
Block: 1067744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181728 RingCT/type: yes/0
Extra: 013bed7b40d5039bb2b3b2010d63ca3018bda6540bf66b2c808bbc16899b2f6103021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da7b3e2a60e6008bb4dfb3722e0b9fea27b85c0c45ce865a7fcd3060e19c82c1 0.600000000000 1538639 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": 1067754, "vin": [ { "gen": { "height": 1067744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da7b3e2a60e6008bb4dfb3722e0b9fea27b85c0c45ce865a7fcd3060e19c82c1" } } ], "extra": [ 1, 59, 237, 123, 64, 213, 3, 155, 178, 179, 178, 1, 13, 99, 202, 48, 24, 189, 166, 84, 11, 246, 107, 44, 128, 139, 188, 22, 137, 155, 47, 97, 3, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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