Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6c5180354594ae2fa88bb64c43dd9d29788da8d5e5cbabc7063643a08929d7

Tx prefix hash: 0a1683d1f9b4e093b9215cb204d8015b5ba5e525fd554ac5a65a7b8c6f04a201
Tx public key: 01f7dd7c79a968aee77971fb0a7be3fcbbf4f757dcc651c80891f62d47b060ba
Timestamp: 1714157769 Timestamp [UCT]: 2024-04-26 18:56:09 Age [y:d:h:m:s]: 00:354:11:23:52
Block: 1009112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253411 RingCT/type: yes/0
Extra: 0101f7dd7c79a968aee77971fb0a7be3fcbbf4f757dcc651c80891f62d47b060ba02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3af2e2313725d21aee5833fe43e22e864edac9c9eca134db08d0e561aab69c01 0.600000000000 1470692 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": 1009122, "vin": [ { "gen": { "height": 1009112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3af2e2313725d21aee5833fe43e22e864edac9c9eca134db08d0e561aab69c01" } } ], "extra": [ 1, 1, 247, 221, 124, 121, 169, 104, 174, 231, 121, 113, 251, 10, 123, 227, 252, 187, 244, 247, 87, 220, 198, 81, 200, 8, 145, 246, 45, 71, 176, 96, 186, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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