Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e36353b27d1b66a35f0fd79544163a7a8f3b85d9ad25702a1f541249da94266

Tx prefix hash: fad414ff437c7a43279bf7ba31f10c4a81a77d3a0089a23736b0213cf75997b4
Tx public key: c7b2afabdd8bdcf47c287d40f3c96246f4ace71b13ddea132d6fcac0b8f4a539
Timestamp: 1707364240 Timestamp [UCT]: 2024-02-08 03:50:40 Age [y:d:h:m:s]: 01:128:02:43:52
Block: 952790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352574 RingCT/type: yes/0
Extra: 01c7b2afabdd8bdcf47c287d40f3c96246f4ace71b13ddea132d6fcac0b8f4a53902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117ff1d4347301dc35148e31b04e038be809f62396e3bc75b91b21be45e1b5f9 0.600000000000 1411920 of 15

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": 952800, "vin": [ { "gen": { "height": 952790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117ff1d4347301dc35148e31b04e038be809f62396e3bc75b91b21be45e1b5f9" } } ], "extra": [ 1, 199, 178, 175, 171, 221, 139, 220, 244, 124, 40, 125, 64, 243, 201, 98, 70, 244, 172, 231, 27, 19, 221, 234, 19, 45, 111, 202, 192, 184, 244, 165, 57, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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