Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fdfbd70a936680134b43264cf820422fa1d20d7b3005b5403ab7632ab6719f1

Tx prefix hash: 442fda8d923b254ee4aa8cd607a73f15c4c0c05261dd4c219b64d8530db810f4
Tx public key: 574acd845db33d873a40d9707063c77c2dfd7987b83c33ee08783ab523190924
Timestamp: 1676329772 Timestamp [UCT]: 2023-02-13 23:09:32 Age [y:d:h:m:s]: 02:010:03:01:42
Block: 696398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528794 RingCT/type: yes/0
Extra: 01574acd845db33d873a40d9707063c77c2dfd7987b83c33ee08783ab5231909240211000000045029cbac000000000000000000

1 output(s) for total of 3.023738683000 dcy

stealth address amount amount idx
00: b8be03f27cc6bc19dff4e072833a5e2dc2729fc5b4d4e6721f9ebccc5a25f71e 3.023738683000 1139395 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": 696408, "vin": [ { "gen": { "height": 696398 } } ], "vout": [ { "amount": 3023738683, "target": { "key": "b8be03f27cc6bc19dff4e072833a5e2dc2729fc5b4d4e6721f9ebccc5a25f71e" } } ], "extra": [ 1, 87, 74, 205, 132, 93, 179, 61, 135, 58, 64, 217, 112, 112, 99, 199, 124, 45, 253, 121, 135, 184, 60, 51, 238, 8, 120, 58, 181, 35, 25, 9, 36, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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