Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf19d679cc621d47d2aa73332ed6b7d05b72955a65a034b5b6c0e144a4265286

Tx prefix hash: 0cff8b93ff869454ede66f45ca57946f6c43a41b08825d514182df9a2804d13a
Tx public key: c0c296e2677adae8f4620874ae79146634650b9625cab114c0d49ad1f348a0f2
Timestamp: 1581246218 Timestamp [UCT]: 2020-02-09 11:03:38 Age [y:d:h:m:s]: 04:270:15:49:52
Block: 61266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085528 RingCT/type: yes/0
Extra: 01c0c296e2677adae8f4620874ae79146634650b9625cab114c0d49ad1f348a0f202110000000f8a2ee0d9000000000000000000

1 output(s) for total of 384.592778960000 dcy

stealth address amount amount idx
00: 7cc3798b07598f59e3c8743948fd5957be538afb84e47a01f346fe4bdb724d7f 384.592778960000 112902 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": 61276, "vin": [ { "gen": { "height": 61266 } } ], "vout": [ { "amount": 384592778960, "target": { "key": "7cc3798b07598f59e3c8743948fd5957be538afb84e47a01f346fe4bdb724d7f" } } ], "extra": [ 1, 192, 194, 150, 226, 103, 122, 218, 232, 244, 98, 8, 116, 174, 121, 20, 102, 52, 101, 11, 150, 37, 202, 177, 20, 192, 212, 154, 209, 243, 72, 160, 242, 2, 17, 0, 0, 0, 15, 138, 46, 224, 217, 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