Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f79e54af2bdcfd27c9457bdbf8ea0959d482b5df69ab6ae6fcb705eca53667

Tx prefix hash: f62081823d70a3c1a0c1c30361e5e3c6410500e0a0a3bf0c8a355037de22dfd1
Tx public key: e7017744cec5be344f553becd629a1aaba65823c503cf48ea8ccca50ebc7b486
Timestamp: 1694984556 Timestamp [UCT]: 2023-09-17 21:02:36 Age [y:d:h:m:s]: 01:271:15:21:17
Block: 850348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455179 RingCT/type: yes/0
Extra: 01e7017744cec5be344f553becd629a1aaba65823c503cf48ea8ccca50ebc7b486021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.934209191000 dcy

stealth address amount amount idx
00: 56cd0b6aa2d13974143bfcfd246f3448181d28c9106dc75d72ce5dcf489a9616 0.934209191000 1304062 of 0

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": 850358, "vin": [ { "gen": { "height": 850348 } } ], "vout": [ { "amount": 934209191, "target": { "key": "56cd0b6aa2d13974143bfcfd246f3448181d28c9106dc75d72ce5dcf489a9616" } } ], "extra": [ 1, 231, 1, 119, 68, 206, 197, 190, 52, 79, 85, 59, 236, 214, 41, 161, 170, 186, 101, 130, 60, 80, 60, 244, 142, 168, 204, 202, 80, 235, 199, 180, 134, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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