Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e53d2c6c423edf5e8d63049afd6dfd1573179c8ea8c77269d5cd189ab077962

Tx prefix hash: 800f39c6851a7ce439a2b58d018246abd19071896520b2df85d0f27a21c2c9c4
Tx public key: 50feb0a0a9f969c74cacfc2d33ee949394d9604714709c7e13d368d991c16574
Timestamp: 1577716236 Timestamp [UCT]: 2019-12-30 14:30:36 Age [y:d:h:m:s]: 05:007:13:28:51
Block: 35093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155391 RingCT/type: yes/0
Extra: 0150feb0a0a9f969c74cacfc2d33ee949394d9604714709c7e13d368d991c165740211000000138a2ee0d9000000000000000000

1 output(s) for total of 469.594690645000 dcy

stealth address amount amount idx
00: aa99de637f5147a9df81315e92839ccbb370f4edde65a919a96e369f388c7147 469.594690645000 59110 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": 35103, "vin": [ { "gen": { "height": 35093 } } ], "vout": [ { "amount": 469594690645, "target": { "key": "aa99de637f5147a9df81315e92839ccbb370f4edde65a919a96e369f388c7147" } } ], "extra": [ 1, 80, 254, 176, 160, 169, 249, 105, 199, 76, 172, 252, 45, 51, 238, 148, 147, 148, 217, 96, 71, 20, 112, 156, 126, 19, 211, 104, 217, 145, 193, 101, 116, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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