Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438eba71e32251ccf4b6bc3574fc2f7047fa972860da103e0af48bfd8131b91f

Tx prefix hash: 7c98d9cd65318b8668ae9bcaa833f022c48d113553ce1fa5ca0e5eb0c8cfcd22
Tx public key: f4543ffde45480f24f93183d9ae126c1a4d2cbc3bcfa56c535325fead69778ed
Timestamp: 1577751037 Timestamp [UCT]: 2019-12-31 00:10:37 Age [y:d:h:m:s]: 05:100:01:45:50
Block: 35384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221274 RingCT/type: yes/0
Extra: 01f4543ffde45480f24f93183d9ae126c1a4d2cbc3bcfa56c535325fead69778ed021100000026c3a1a09f000000000000000000

1 output(s) for total of 468.605970716000 dcy

stealth address amount amount idx
00: ec201660217f935b321e3f5c0757dab463d962fd55a4dfb69f78b9817921c3d0 468.605970716000 59636 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": 35394, "vin": [ { "gen": { "height": 35384 } } ], "vout": [ { "amount": 468605970716, "target": { "key": "ec201660217f935b321e3f5c0757dab463d962fd55a4dfb69f78b9817921c3d0" } } ], "extra": [ 1, 244, 84, 63, 253, 228, 84, 128, 242, 79, 147, 24, 61, 154, 225, 38, 193, 164, 210, 203, 195, 188, 250, 86, 197, 53, 50, 95, 234, 214, 151, 120, 237, 2, 17, 0, 0, 0, 38, 195, 161, 160, 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