Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f254ba7c5cda028c01672355c7b8f30518e3ef935cf23a289163aa0756a740b7

Tx prefix hash: 4b946afb06ca64a301b949f4ff16d68f129197c1852954b38c1f0132d8f48be8
Tx public key: 5ab0e9e5004c55f492ffa16c674605794a2dcf9174c295ef91d9779f54766f33
Timestamp: 1667364203 Timestamp [UCT]: 2022-11-02 04:43:23 Age [y:d:h:m:s]: 02:014:20:35:08
Block: 622170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532470 RingCT/type: yes/0
Extra: 015ab0e9e5004c55f492ffa16c674605794a2dcf9174c295ef91d9779f54766f3302110000000ae6d27f9c000000000000000000

1 output(s) for total of 5.327120765000 dcy

stealth address amount amount idx
00: f1d2cbb486c76bd20b3f2f32888b779d531cb098d1581a7ad1319c0f9982b80e 5.327120765000 1060231 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": 622180, "vin": [ { "gen": { "height": 622170 } } ], "vout": [ { "amount": 5327120765, "target": { "key": "f1d2cbb486c76bd20b3f2f32888b779d531cb098d1581a7ad1319c0f9982b80e" } } ], "extra": [ 1, 90, 176, 233, 229, 0, 76, 85, 244, 146, 255, 161, 108, 103, 70, 5, 121, 74, 45, 207, 145, 116, 194, 149, 239, 145, 217, 119, 159, 84, 118, 111, 51, 2, 17, 0, 0, 0, 10, 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