Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddcd6f8b4ee8ee03818ca202825a6889821183da7ac01d239ac9350f23a82cd9

Tx prefix hash: f2a8d3248593795790e5e857ea303b9fdf363ec1421fa2adee49d961a1c7da1a
Tx public key: 86d44fc2986a67bbff314cf218555e7acc59068c3f9ae371929b29c44b831fa4
Timestamp: 1717772350 Timestamp [UCT]: 2024-06-07 14:59:10 Age [y:d:h:m:s]: 00:281:08:22:06
Block: 1039100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201074 RingCT/type: yes/0
Extra: 0186d44fc2986a67bbff314cf218555e7acc59068c3f9ae371929b29c44b831fa402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4e39bcb5ca148628bdc135fdc9c80e8b51347ea63920eec04ff94e85a8c9cfa 0.600000000000 1507693 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": 1039110, "vin": [ { "gen": { "height": 1039100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e39bcb5ca148628bdc135fdc9c80e8b51347ea63920eec04ff94e85a8c9cfa" } } ], "extra": [ 1, 134, 212, 79, 194, 152, 106, 103, 187, 255, 49, 76, 242, 24, 85, 94, 122, 204, 89, 6, 140, 63, 154, 227, 113, 146, 155, 41, 196, 75, 131, 31, 164, 2, 17, 0, 0, 0, 6, 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