Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de88ec706eb3425058b1aaecb5bee8503c19c623aedaa530de4bcd1672fecdb

Tx prefix hash: fc0d67c7eac8bed0803a7ecd6acf9519fdb17afcf049b3cbf59e9aa95c117ade
Tx public key: e1ce0b57d7e74059d3ae45823cb8c1b51069e17e0ca551977381145593b1cca2
Timestamp: 1577729148 Timestamp [UCT]: 2019-12-30 18:05:48 Age [y:d:h:m:s]: 05:065:02:43:36
Block: 35220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196264 RingCT/type: yes/0
Extra: 01e1ce0b57d7e74059d3ae45823cb8c1b51069e17e0ca551977381145593b1cca20211000000018a2ee0d9000000000000000000

1 output(s) for total of 469.139903433000 dcy

stealth address amount amount idx
00: c813a0345554ef9063e5e7cd2799ff8d45f2f89530afdda2c7dddcd568f09919 469.139903433000 59310 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": 35230, "vin": [ { "gen": { "height": 35220 } } ], "vout": [ { "amount": 469139903433, "target": { "key": "c813a0345554ef9063e5e7cd2799ff8d45f2f89530afdda2c7dddcd568f09919" } } ], "extra": [ 1, 225, 206, 11, 87, 215, 231, 64, 89, 211, 174, 69, 130, 60, 184, 193, 181, 16, 105, 225, 126, 12, 165, 81, 151, 115, 129, 20, 85, 147, 177, 204, 162, 2, 17, 0, 0, 0, 1, 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