Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48deb452f82083b1ed8e69eed57dc6a1ef1eadac8a7e8e182347984e28e056a6

Tx prefix hash: 4fb5f9c11245c22dc72c03647cfa93186dadfba9df261e4d61d5cfd577052343
Tx public key: ad54ccd17e5eea57de825b25bce03f00138a2ced808f32c7d37cd233e29c3355
Timestamp: 1710152798 Timestamp [UCT]: 2024-03-11 10:26:38 Age [y:d:h:m:s]: 01:014:05:49:22
Block: 975929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271153 RingCT/type: yes/0
Extra: 01ad54ccd17e5eea57de825b25bce03f00138a2ced808f32c7d37cd233e29c33550211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc19bf16d3d3fb5f18e84a3c38613ee9e10ad47bef1a30945abc10e8cb8a55ca 0.600000000000 1435906 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": 975939, "vin": [ { "gen": { "height": 975929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc19bf16d3d3fb5f18e84a3c38613ee9e10ad47bef1a30945abc10e8cb8a55ca" } } ], "extra": [ 1, 173, 84, 204, 209, 126, 94, 234, 87, 222, 130, 91, 37, 188, 224, 63, 0, 19, 138, 44, 237, 128, 143, 50, 199, 211, 124, 210, 51, 226, 156, 51, 85, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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