Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f743bdc9befaf1deddc9d16dbfcfac27c60079689bb5741d223595164c9cdf24

Tx prefix hash: 8cf5364e28038eb413b786cd3ff74255d2a6e8a4f2fe829711c29ec77c762560
Tx public key: 2cb49a35db75b0a0e7d96854c4ffd5ea54b4cc93e8f854ea1f5a1efb2d038bc3
Timestamp: 1576281670 Timestamp [UCT]: 2019-12-14 00:01:10 Age [y:d:h:m:s]: 04:355:01:57:26
Block: 26516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139583 RingCT/type: yes/0
Extra: 012cb49a35db75b0a0e7d96854c4ffd5ea54b4cc93e8f854ea1f5a1efb2d038bc3021100000013ad433a0b000000000000000000

1 output(s) for total of 501.351538584000 dcy

stealth address amount amount idx
00: 510009e135c42bac9fe9601e7d0248474e5829bce074d2e9c0ea5fa4a6e88281 501.351538584000 43957 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": 26526, "vin": [ { "gen": { "height": 26516 } } ], "vout": [ { "amount": 501351538584, "target": { "key": "510009e135c42bac9fe9601e7d0248474e5829bce074d2e9c0ea5fa4a6e88281" } } ], "extra": [ 1, 44, 180, 154, 53, 219, 117, 176, 160, 231, 217, 104, 84, 196, 255, 213, 234, 84, 180, 204, 147, 232, 248, 84, 234, 31, 90, 30, 251, 45, 3, 139, 195, 2, 17, 0, 0, 0, 19, 173, 67, 58, 11, 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