Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b3f765918ff71f49e66e77a79c8c34757d10962104ed0e04715a2c537be299

Tx prefix hash: 37dbc296034fa6423b8bcebd254938e0ea1984bae6ee000e9d7e436c1dddf440
Tx public key: e5d355e18143354c6b910884e79e0798bcf1343aa1cd7a60c37e75f532497ad7
Timestamp: 1643254951 Timestamp [UCT]: 2022-01-27 03:42:31 Age [y:d:h:m:s]: 03:001:02:47:35
Block: 426104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779952 RingCT/type: yes/0
Extra: 01e5d355e18143354c6b910884e79e0798bcf1343aa1cd7a60c37e75f532497ad702110000000ee778ec4c000000000000000000

1 output(s) for total of 23.776114174000 dcy

stealth address amount amount idx
00: 1d47eaa403f6b75917ef4f71585500aa038e0e0c1ff0c23427af0a17d7970244 23.776114174000 834889 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": 426114, "vin": [ { "gen": { "height": 426104 } } ], "vout": [ { "amount": 23776114174, "target": { "key": "1d47eaa403f6b75917ef4f71585500aa038e0e0c1ff0c23427af0a17d7970244" } } ], "extra": [ 1, 229, 211, 85, 225, 129, 67, 53, 76, 107, 145, 8, 132, 231, 158, 7, 152, 188, 241, 52, 58, 161, 205, 122, 96, 195, 126, 117, 245, 50, 73, 122, 215, 2, 17, 0, 0, 0, 14, 231, 120, 236, 76, 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