Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a6816ab2b409830a8c68dea0e45a605fdfb25cf2a3214513d7e4dc6e558bb8

Tx prefix hash: 96aec977d9ec3598daa770ed9c149cbba8d68e4b2b62e5f9d8bd79fb36be624b
Tx public key: 029d1a6491337edc3ee9a489a502bbb4fddcb22491f5ed9fc5ddf465505ac2f1
Timestamp: 1577997065 Timestamp [UCT]: 2020-01-02 20:31:05 Age [y:d:h:m:s]: 05:061:23:44:57
Block: 37413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194055 RingCT/type: yes/0
Extra: 01029d1a6491337edc3ee9a489a502bbb4fddcb22491f5ed9fc5ddf465505ac2f10211000000204943cd9f000000000000000000

1 output(s) for total of 461.355870933000 dcy

stealth address amount amount idx
00: 1ba32ac4920fe1909d5550f7fc277e3c22c1d4bf29827fcf5ed2fd8d25b9b660 461.355870933000 63499 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": 37423, "vin": [ { "gen": { "height": 37413 } } ], "vout": [ { "amount": 461355870933, "target": { "key": "1ba32ac4920fe1909d5550f7fc277e3c22c1d4bf29827fcf5ed2fd8d25b9b660" } } ], "extra": [ 1, 2, 157, 26, 100, 145, 51, 126, 220, 62, 233, 164, 137, 165, 2, 187, 180, 253, 220, 178, 36, 145, 245, 237, 159, 197, 221, 244, 101, 80, 90, 194, 241, 2, 17, 0, 0, 0, 32, 73, 67, 205, 159, 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