Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24bdeb9197ec9a9dd1fba1d575bf1ab2122d85238e69d79714cde1783761751

Tx prefix hash: 9ac1f105c99de6b87d0715c4002882cbb0b16950444e036518e72b95d8fe5311
Tx public key: 07baf4a2ceca95a74e72d02b30a638dd8f6053b06c8cf04d2b93105edd15d251
Timestamp: 1727912984 Timestamp [UCT]: 2024-10-02 23:49:44 Age [y:d:h:m:s]: 00:241:03:34:00
Block: 1123158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172191 RingCT/type: yes/0
Extra: 0107baf4a2ceca95a74e72d02b30a638dd8f6053b06c8cf04d2b93105edd15d251021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fef1a8b2fb605accd48a3f1f2830117a7a7f2af05809e63ca1ab55b1b96e6be 0.600000000000 1605691 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": 1123168, "vin": [ { "gen": { "height": 1123158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fef1a8b2fb605accd48a3f1f2830117a7a7f2af05809e63ca1ab55b1b96e6be" } } ], "extra": [ 1, 7, 186, 244, 162, 206, 202, 149, 167, 78, 114, 208, 43, 48, 166, 56, 221, 143, 96, 83, 176, 108, 140, 240, 77, 43, 147, 16, 94, 221, 21, 210, 81, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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