Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d73f5bb9a4c0bfc3cea32577840735f84a48c7f3b1157f66b4cf1d47c624462

Tx prefix hash: 970d9f4c78bad2c74c1b3eb75b69d033bea624923b8652146d613c4471651540
Tx public key: 61bd879a32cd85a35aa702bdccec4ee961afc0c98467d44c4f970b8353bd3de0
Timestamp: 1581271765 Timestamp [UCT]: 2020-02-09 18:09:25 Age [y:d:h:m:s]: 04:270:21:21:08
Block: 61638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085537 RingCT/type: yes/0
Extra: 0161bd879a32cd85a35aa702bdccec4ee961afc0c98467d44c4f970b8353bd3de00211000000064ac5aa02000000000000000000

1 output(s) for total of 383.502796156000 dcy

stealth address amount amount idx
00: b121d70b2e05c1170dbe7238d5369729dac4e8363561d6071ecc36fb27b32295 383.502796156000 113636 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": 61648, "vin": [ { "gen": { "height": 61638 } } ], "vout": [ { "amount": 383502796156, "target": { "key": "b121d70b2e05c1170dbe7238d5369729dac4e8363561d6071ecc36fb27b32295" } } ], "extra": [ 1, 97, 189, 135, 154, 50, 205, 133, 163, 90, 167, 2, 189, 204, 236, 78, 233, 97, 175, 192, 201, 132, 103, 212, 76, 79, 151, 11, 131, 83, 189, 61, 224, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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