Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018df9812327b06e4c686c6bc0b2d1dbab9a8bf0886976336c697e1d7ed25ade

Tx prefix hash: f14aea6bd2f8a9850b7e21a4a80b5a64a9769a8d25a7f25014cd77fa29b9f131
Tx public key: 3fbd02b4b3a0d50f1c8e3266e4dc76a7ce7f09f87c917854127785f7691f67a8
Timestamp: 1710715750 Timestamp [UCT]: 2024-03-17 22:49:10 Age [y:d:h:m:s]: 00:187:18:01:47
Block: 980607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134459 RingCT/type: yes/0
Extra: 013fbd02b4b3a0d50f1c8e3266e4dc76a7ce7f09f87c917854127785f7691f67a802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a580ed4d0a3a54a6b02fa490b2b4b7cabd6c27d7ac3a364d07eb590613556a47 0.600000000000 1440686 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": 980617, "vin": [ { "gen": { "height": 980607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a580ed4d0a3a54a6b02fa490b2b4b7cabd6c27d7ac3a364d07eb590613556a47" } } ], "extra": [ 1, 63, 189, 2, 180, 179, 160, 213, 15, 28, 142, 50, 102, 228, 220, 118, 167, 206, 127, 9, 248, 124, 145, 120, 84, 18, 119, 133, 247, 105, 31, 103, 168, 2, 17, 0, 0, 0, 6, 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