Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 783d867e6d77dbd4c13e9e098a762ee05a1a483cdcaa7b0093e9dafd1cfc03c7

Tx prefix hash: b8caa5332cdfb183f058d19da71e29bb3a5734a5cbbe7d0617d603b018f588f2
Tx public key: 4168a2d6e36d85492fbd42f69f6d968f2ce1e904e151de03d4c05586b4f6a514
Timestamp: 1709895022 Timestamp [UCT]: 2024-03-08 10:50:22 Age [y:d:h:m:s]: 01:257:01:08:31
Block: 973796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442420 RingCT/type: yes/0
Extra: 014168a2d6e36d85492fbd42f69f6d968f2ce1e904e151de03d4c05586b4f6a51402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ffad557a698f501d4af1349f871e3b6831cac4b72024caeea7e4fe69d7864eb 0.600000000000 1433735 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": 973806, "vin": [ { "gen": { "height": 973796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ffad557a698f501d4af1349f871e3b6831cac4b72024caeea7e4fe69d7864eb" } } ], "extra": [ 1, 65, 104, 162, 214, 227, 109, 133, 73, 47, 189, 66, 246, 159, 109, 150, 143, 44, 225, 233, 4, 225, 81, 222, 3, 212, 192, 85, 134, 180, 246, 165, 20, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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