Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21221db11f00a0ae384fd66c7043ecc797bac39f4073a117c71e4fe6d9a3e7b6

Tx prefix hash: c098adb8d0d1373b255bbf102fd4ac4b3630df68dd5b96cc23523e5e11a66c71
Tx public key: 8f934d80740b262e06e9c0b9ba0b1192b24b985fc2690a5950b6c9c8b86c3e05
Timestamp: 1713254283 Timestamp [UCT]: 2024-04-16 07:58:03 Age [y:d:h:m:s]: 00:208:22:24:59
Block: 1001610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149589 RingCT/type: yes/0
Extra: 018f934d80740b262e06e9c0b9ba0b1192b24b985fc2690a5950b6c9c8b86c3e0502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dedb05c0a7e6d713d7b54c8b91ec07cdc8342cb469ca27859015c3ca368c8fb2 0.600000000000 1462116 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": 1001620, "vin": [ { "gen": { "height": 1001610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dedb05c0a7e6d713d7b54c8b91ec07cdc8342cb469ca27859015c3ca368c8fb2" } } ], "extra": [ 1, 143, 147, 77, 128, 116, 11, 38, 46, 6, 233, 192, 185, 186, 11, 17, 146, 178, 75, 152, 95, 194, 105, 10, 89, 80, 182, 201, 200, 184, 108, 62, 5, 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