Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6e4effc9ad21a821888b109b15f7b7850834ea78f23170408861e3c136c572

Tx prefix hash: b69df5dc41429bbae43417f110a17d4464ad9e4b82fc1e12327a70d53502be58
Tx public key: 3b9d8e0933f17e8813050fb282404a1495b4110a43696b2c09093b32cd45b07c
Timestamp: 1673038649 Timestamp [UCT]: 2023-01-06 20:57:29 Age [y:d:h:m:s]: 01:316:03:05:11
Block: 669080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486945 RingCT/type: yes/0
Extra: 013b9d8e0933f17e8813050fb282404a1495b4110a43696b2c09093b32cd45b07c02110000000152542ceb000000000000000000

1 output(s) for total of 3.724433036000 dcy

stealth address amount amount idx
00: adb2a9ad75ad54021f1b85dc188aed17052287c84109e2d051bb3df0ebf6ae98 3.724433036000 1110371 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": 669090, "vin": [ { "gen": { "height": 669080 } } ], "vout": [ { "amount": 3724433036, "target": { "key": "adb2a9ad75ad54021f1b85dc188aed17052287c84109e2d051bb3df0ebf6ae98" } } ], "extra": [ 1, 59, 157, 142, 9, 51, 241, 126, 136, 19, 5, 15, 178, 130, 64, 74, 20, 149, 180, 17, 10, 67, 105, 107, 44, 9, 9, 59, 50, 205, 69, 176, 124, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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