Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50612299480c608c3324a9deef3fd8d01886cb364a4acc022d9e09100005bcb

Tx prefix hash: effbb61f8adf5ea36cdbbd741a3fd72810bf6c05a8bbea8cf460f2abd1b5308c
Tx public key: b4bab33674d7b8bcfd4d1a8c8cf2b3462d3732780f5d870bb4e073afbca8122a
Timestamp: 1693577018 Timestamp [UCT]: 2023-09-01 14:03:38 Age [y:d:h:m:s]: 01:176:17:24:19
Block: 838676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387387 RingCT/type: yes/0
Extra: 01b4bab33674d7b8bcfd4d1a8c8cf2b3462d3732780f5d870bb4e073afbca8122a02110000000dfaf35c9c000000000000000000

1 output(s) for total of 1.021217702000 dcy

stealth address amount amount idx
00: e970e4800dca89a21255d59d60f7c6fee29287a79df6adbb400262c5eb339e64 1.021217702000 1291446 of 0

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": 838686, "vin": [ { "gen": { "height": 838676 } } ], "vout": [ { "amount": 1021217702, "target": { "key": "e970e4800dca89a21255d59d60f7c6fee29287a79df6adbb400262c5eb339e64" } } ], "extra": [ 1, 180, 186, 179, 54, 116, 215, 184, 188, 253, 77, 26, 140, 140, 242, 179, 70, 45, 55, 50, 120, 15, 93, 135, 11, 180, 224, 115, 175, 188, 168, 18, 42, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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