Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95dafdc5a4252e5b4ded57e304e6f24e3e19eab2b8b86102a3000a213803f13b

Tx prefix hash: 1586028c617981e946ecd4d43f7c6d28c742dea486fb44c3efb418d5de372d25
Tx public key: e48062358a5586510e123bb4817c41e4739a7e5974d87e30d9e5c50b85982f7a
Timestamp: 1728181740 Timestamp [UCT]: 2024-10-06 02:29:00 Age [y:d:h:m:s]: 00:180:05:59:08
Block: 1125387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128617 RingCT/type: yes/0
Extra: 01e48062358a5586510e123bb4817c41e4739a7e5974d87e30d9e5c50b85982f7a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed939201ed485abd2f8d890e3ec5d67d73ca7d4e5a3fc5379dd6c7f03c49763 0.600000000000 1608068 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": 1125397, "vin": [ { "gen": { "height": 1125387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed939201ed485abd2f8d890e3ec5d67d73ca7d4e5a3fc5379dd6c7f03c49763" } } ], "extra": [ 1, 228, 128, 98, 53, 138, 85, 134, 81, 14, 18, 59, 180, 129, 124, 65, 228, 115, 154, 126, 89, 116, 216, 126, 48, 217, 229, 197, 11, 133, 152, 47, 122, 2, 17, 0, 0, 0, 2, 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