Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc8be88a1277bac1450bf535c46ddc3d595e928e1e57bf5e54f2c05263c9ca61

Tx prefix hash: c2f4d5dea876c7e6146c73df776532569278e3f6dd80435767ce9712edf33fba
Tx public key: cf6d249dd27771e094d689de3a15787aaea10caa8a5687232a0e69558e2991b0
Timestamp: 1722956396 Timestamp [UCT]: 2024-08-06 14:59:56 Age [y:d:h:m:s]: 00:291:04:05:57
Block: 1082058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208028 RingCT/type: yes/0
Extra: 01cf6d249dd27771e094d689de3a15787aaea10caa8a5687232a0e69558e2991b0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc0684b9a8477a215acdb6761387276e50135b5eaa3924870680b1674e1fe8f9 0.600000000000 1555881 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": 1082068, "vin": [ { "gen": { "height": 1082058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc0684b9a8477a215acdb6761387276e50135b5eaa3924870680b1674e1fe8f9" } } ], "extra": [ 1, 207, 109, 36, 157, 210, 119, 113, 224, 148, 214, 137, 222, 58, 21, 120, 122, 174, 161, 12, 170, 138, 86, 135, 35, 42, 14, 105, 85, 142, 41, 145, 176, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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