Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 318e70836d9405277c91c78fdb09894fc9a9a8b1cd63fb3a6a68e597b859b690

Tx prefix hash: c0238e34b997153459e1c0fbe3cc372ade3e22f85f4d9a3672265c3d9d76c008
Tx public key: 0ba9c690bfb19f97c345f8dbb9b79bab1a8d3382d80e39585596d9fd3ee5037d
Timestamp: 1736308442 Timestamp [UCT]: 2025-01-08 03:54:02 Age [y:d:h:m:s]: 00:296:03:32:27
Block: 1192623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209157 RingCT/type: yes/0
Extra: 010ba9c690bfb19f97c345f8dbb9b79bab1a8d3382d80e39585596d9fd3ee5037d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73517e4af7a7164b3ca007de8b184e7f8412e7ed74d5ad91b121072d4c3927af 0.600000000000 1679178 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": 1192633, "vin": [ { "gen": { "height": 1192623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73517e4af7a7164b3ca007de8b184e7f8412e7ed74d5ad91b121072d4c3927af" } } ], "extra": [ 1, 11, 169, 198, 144, 191, 177, 159, 151, 195, 69, 248, 219, 185, 183, 155, 171, 26, 141, 51, 130, 216, 14, 57, 88, 85, 150, 217, 253, 62, 229, 3, 125, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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