Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c0bd25eee182abaa1040e4227487efde4180d38fe3b8c6f2c80383c3648387

Tx prefix hash: 027e741ba4a9c84d16919762d85c8252f235f3be656e153a59be0c7776238e45
Tx public key: b4cfcc9a70fe7d2487804bca3e6293193079db2e1b1a65b70ed863e592bff6b4
Timestamp: 1725385124 Timestamp [UCT]: 2024-09-03 17:38:44 Age [y:d:h:m:s]: 00:218:12:32:54
Block: 1102202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156026 RingCT/type: yes/0
Extra: 01b4cfcc9a70fe7d2487804bca3e6293193079db2e1b1a65b70ed863e592bff6b402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f7289aea2d84b8a3a2187a39382eda1fcd7d9b4dd351602e3d61c1df7a32d11 0.600000000000 1578547 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": 1102212, "vin": [ { "gen": { "height": 1102202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f7289aea2d84b8a3a2187a39382eda1fcd7d9b4dd351602e3d61c1df7a32d11" } } ], "extra": [ 1, 180, 207, 204, 154, 112, 254, 125, 36, 135, 128, 75, 202, 62, 98, 147, 25, 48, 121, 219, 46, 27, 26, 101, 183, 14, 216, 99, 229, 146, 191, 246, 180, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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