Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c462ee540a09f0e6d434e870822f3cdb5cf2b33f1ef0be21c018bb3400d4a4d9

Tx prefix hash: 12a5adf3aee479f27ebc18d53e70f2ce7813e6e998e2ee6e0e97250b4a76eebd
Tx public key: 8f6fda379f4fd3a794798dc1f8af4cda5ee21695a95e39f3310d3583f12b09a4
Timestamp: 1704267444 Timestamp [UCT]: 2024-01-03 07:37:24 Age [y:d:h:m:s]: 01:057:10:26:59
Block: 927118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302130 RingCT/type: yes/0
Extra: 018f6fda379f4fd3a794798dc1f8af4cda5ee21695a95e39f3310d3583f12b09a402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 235d59b7554fb1a049a2f04984d710ab87014928a8497eadb1f2cba074a6f1cb 0.600000000000 1384922 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": 927128, "vin": [ { "gen": { "height": 927118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "235d59b7554fb1a049a2f04984d710ab87014928a8497eadb1f2cba074a6f1cb" } } ], "extra": [ 1, 143, 111, 218, 55, 159, 79, 211, 167, 148, 121, 141, 193, 248, 175, 76, 218, 94, 226, 22, 149, 169, 94, 57, 243, 49, 13, 53, 131, 241, 43, 9, 164, 2, 17, 0, 0, 0, 2, 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