Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e42e202a008ae523c82db84e16f1fe49079d1a36266d2bf6ddb11726b430566

Tx prefix hash: 187fe3229d8047a218d71f73420e6fdcf97f7d95a7bb780906769b55f0ffb306
Tx public key: 4074b4a01a9cf5fcd3be8fa6992e31de87cd4a4a1d0bf16b7fd8e0ae4201f8a0
Timestamp: 1714340895 Timestamp [UCT]: 2024-04-28 21:48:15 Age [y:d:h:m:s]: 00:324:12:46:21
Block: 1010632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232012 RingCT/type: yes/0
Extra: 014074b4a01a9cf5fcd3be8fa6992e31de87cd4a4a1d0bf16b7fd8e0ae4201f8a002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b79b021f0ba2de82c4fa00071fab9de75d9d52df9b844ecc580cb2d9e8e4a97 0.600000000000 1472642 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": 1010642, "vin": [ { "gen": { "height": 1010632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b79b021f0ba2de82c4fa00071fab9de75d9d52df9b844ecc580cb2d9e8e4a97" } } ], "extra": [ 1, 64, 116, 180, 160, 26, 156, 245, 252, 211, 190, 143, 166, 153, 46, 49, 222, 135, 205, 74, 74, 29, 11, 241, 107, 127, 216, 224, 174, 66, 1, 248, 160, 2, 17, 0, 0, 0, 1, 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