Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c46c04c690fe21815d2cbc26d0ee4dc9e2186cb7397bb5212d28b09b837fd1

Tx prefix hash: 4bda802cbff4293e082e865feedcad681683ed739f5b655bd309f0f992554e89
Tx public key: 4bfea2aafcd82bebca59de9c608a8e07a21d2f0cf8b93f3f627611158ce1c7ab
Timestamp: 1729750869 Timestamp [UCT]: 2024-10-24 06:21:09 Age [y:d:h:m:s]: 00:149:08:11:48
Block: 1138365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106528 RingCT/type: yes/0
Extra: 014bfea2aafcd82bebca59de9c608a8e07a21d2f0cf8b93f3f627611158ce1c7ab021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05faf1c477cfc927f0f282926892230af5d621404a4135f94f406ecb0857fb62 0.600000000000 1622010 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": 1138375, "vin": [ { "gen": { "height": 1138365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05faf1c477cfc927f0f282926892230af5d621404a4135f94f406ecb0857fb62" } } ], "extra": [ 1, 75, 254, 162, 170, 252, 216, 43, 235, 202, 89, 222, 156, 96, 138, 142, 7, 162, 29, 47, 12, 248, 185, 63, 63, 98, 118, 17, 21, 140, 225, 199, 171, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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