Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064a0421176c4c6c8eaff915da50e0f77ce32ffc532d6825a414f42e079d9e41

Tx prefix hash: d00fcb4c9237227836d5ddc4c6aa86bf94ab2c2ae8665863f91387e4cb215029
Tx public key: e5a137c35c41c8f240a95c24a0db2ee5ba70cf82734ee90491976eadb325cd9e
Timestamp: 1582333652 Timestamp [UCT]: 2020-02-22 01:07:32 Age [y:d:h:m:s]: 05:079:00:50:48
Block: 69804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209765 RingCT/type: yes/0
Extra: 01e5a137c35c41c8f240a95c24a0db2ee5ba70cf82734ee90491976eadb325cd9e02110000000203d36d11000000000000000000

1 output(s) for total of 360.338921986000 dcy

stealth address amount amount idx
00: 3086e69d21a0909cb733ecd81e868dd0e4ad033ff07dd99c5399a341980f69d4 360.338921986000 128838 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": 69814, "vin": [ { "gen": { "height": 69804 } } ], "vout": [ { "amount": 360338921986, "target": { "key": "3086e69d21a0909cb733ecd81e868dd0e4ad033ff07dd99c5399a341980f69d4" } } ], "extra": [ 1, 229, 161, 55, 195, 92, 65, 200, 242, 64, 169, 92, 36, 160, 219, 46, 229, 186, 112, 207, 130, 115, 78, 233, 4, 145, 151, 110, 173, 179, 37, 205, 158, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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