Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ae092a84b0bbc78e06bc90e357ac1a4a68d3833ef3f2c9f2cb4742fc531ea0

Tx prefix hash: 40998fb5627c9b1541920aaf3d14fe29301162fdcba741f932bcccc2b0df80c0
Tx public key: 48142a246b0e24bbe1000a686888eaf01aa7b293e8edc536df69449773cf26df
Timestamp: 1617555055 Timestamp [UCT]: 2021-04-04 16:50:55 Age [y:d:h:m:s]: 03:277:20:56:01
Block: 233151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 958344 RingCT/type: yes/0
Extra: 0148142a246b0e24bbe1000a686888eaf01aa7b293e8edc536df69449773cf26df02110000003190ec05ad000000000000000000

1 output(s) for total of 103.627382464000 dcy

stealth address amount amount idx
00: 7bafa8cb86ce9f342d83b088285c98be2e38e60017e5238921708e0414fa7a83 103.627382464000 484251 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": 233161, "vin": [ { "gen": { "height": 233151 } } ], "vout": [ { "amount": 103627382464, "target": { "key": "7bafa8cb86ce9f342d83b088285c98be2e38e60017e5238921708e0414fa7a83" } } ], "extra": [ 1, 72, 20, 42, 36, 107, 14, 36, 187, 225, 0, 10, 104, 104, 136, 234, 240, 26, 167, 178, 147, 232, 237, 197, 54, 223, 105, 68, 151, 115, 207, 38, 223, 2, 17, 0, 0, 0, 49, 144, 236, 5, 173, 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