Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c78ea882d5544c460d1513452527d098ee696456f1598bc81d2a00f3884937

Tx prefix hash: e9cad6733fd718b5ef1e2b8d3842e0fbfd4bebd43a49e5a47a01c1727efda899
Tx public key: bee1cce7ab19a551d168300a6d1c9fd9399d29279485a5f66f8075156d24ea3c
Timestamp: 1705867489 Timestamp [UCT]: 2024-01-21 20:04:49 Age [y:d:h:m:s]: 01:093:21:14:56
Block: 940362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328217 RingCT/type: yes/0
Extra: 01bee1cce7ab19a551d168300a6d1c9fd9399d29279485a5f66f8075156d24ea3c02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbb9ef63c9c84d455a7d9f88f3fb506107ba449079554c624f41ad88328a4884 0.600000000000 1398498 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": 940372, "vin": [ { "gen": { "height": 940362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb9ef63c9c84d455a7d9f88f3fb506107ba449079554c624f41ad88328a4884" } } ], "extra": [ 1, 190, 225, 204, 231, 171, 25, 165, 81, 209, 104, 48, 10, 109, 28, 159, 217, 57, 157, 41, 39, 148, 133, 165, 246, 111, 128, 117, 21, 109, 36, 234, 60, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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