Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b575f33a717e6e0db9ee9075b7587532e75333b0865b425a8fd79e54f7190fa

Tx prefix hash: 116e06b1d5af5f2b0d3bae75edcd3fdfa603c6c2e4694de658fba3b34575b732
Tx public key: 8ba9b1a38d3340810926493381a9ab9d324364ee83f8a3c34628e1ef2bf79060
Timestamp: 1608901914 Timestamp [UCT]: 2020-12-25 13:11:54 Age [y:d:h:m:s]: 03:323:18:03:12
Block: 169166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 983481 RingCT/type: yes/0
Extra: 018ba9b1a38d3340810926493381a9ab9d324364ee83f8a3c34628e1ef2bf790600211000002fd90ce5c0f000000000000000000

1 output(s) for total of 168.843165141000 dcy

stealth address amount amount idx
00: bb050fa74b69702b50546c98fd5320e4cd85f51daaaa9cbd020d00510468fa64 168.843165141000 315221 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": 169176, "vin": [ { "gen": { "height": 169166 } } ], "vout": [ { "amount": 168843165141, "target": { "key": "bb050fa74b69702b50546c98fd5320e4cd85f51daaaa9cbd020d00510468fa64" } } ], "extra": [ 1, 139, 169, 177, 163, 141, 51, 64, 129, 9, 38, 73, 51, 129, 169, 171, 157, 50, 67, 100, 238, 131, 248, 163, 195, 70, 40, 225, 239, 43, 247, 144, 96, 2, 17, 0, 0, 2, 253, 144, 206, 92, 15, 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