Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c378c6fd6ef6f4e23281ec16e2c79c4fb1aedff44314e6cd0af78b8787bee46

Tx prefix hash: 836e27eccc0d37d0e2d3d03ebd722691ade458a99dce24400d5e205025376cd9
Tx public key: aa908c188136e8fc95208f2b4ef4d5bdb424ec022cfc168ffc74582c2f47eef8
Timestamp: 1721431514 Timestamp [UCT]: 2024-07-19 23:25:14 Age [y:d:h:m:s]: 00:300:14:17:50
Block: 1069467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214736 RingCT/type: yes/0
Extra: 01aa908c188136e8fc95208f2b4ef4d5bdb424ec022cfc168ffc74582c2f47eef80211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 707c26b890084806f078a5bee8b4cce6ddea72806887a7a6bdd412bb938a98ef 0.600000000000 1540892 of 15

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": 1069477, "vin": [ { "gen": { "height": 1069467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "707c26b890084806f078a5bee8b4cce6ddea72806887a7a6bdd412bb938a98ef" } } ], "extra": [ 1, 170, 144, 140, 24, 129, 54, 232, 252, 149, 32, 143, 43, 78, 244, 213, 189, 180, 36, 236, 2, 44, 252, 22, 143, 252, 116, 88, 44, 47, 71, 238, 248, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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