Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0f1cf8817abdf909235f7383361520fe1e6101797fe68c624b45ae9cd7b4b9f

Tx prefix hash: 4e98a52f27b68d374f2bc77673308247dd5840f3a6c8720f099ad2f8b39258e0
Tx public key: 65b7579333d763d14f6b3f8c5e24e345a751284adc7b0b0726f8e928a5f4fae5
Timestamp: 1584924558 Timestamp [UCT]: 2020-03-23 00:49:18 Age [y:d:h:m:s]: 05:028:07:15:35
Block: 87086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177638 RingCT/type: yes/0
Extra: 0165b7579333d763d14f6b3f8c5e24e345a751284adc7b0b0726f8e928a5f4fae502110000007a69b04ac4000000000000000000

1 output(s) for total of 315.826603972000 dcy

stealth address amount amount idx
00: d42cf3aaab4d3b745f13536757317df75f934291d80eea7b39075932efdbfc05 315.826603972000 157002 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": 87096, "vin": [ { "gen": { "height": 87086 } } ], "vout": [ { "amount": 315826603972, "target": { "key": "d42cf3aaab4d3b745f13536757317df75f934291d80eea7b39075932efdbfc05" } } ], "extra": [ 1, 101, 183, 87, 147, 51, 215, 99, 209, 79, 107, 63, 140, 94, 36, 227, 69, 167, 81, 40, 74, 220, 123, 11, 7, 38, 248, 233, 40, 165, 244, 250, 229, 2, 17, 0, 0, 0, 122, 105, 176, 74, 196, 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