Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78ab333f74f18d27331ba7dde242bd8d4fe148ece3de3358e4a04961fbf0809b

Tx prefix hash: 8044affa39a97281c6ca49c54328d3078256dbbb7b0b0da9d563cb54f49191d8
Tx public key: dd2b21f89ec173f2b8a5d9b9f47d29f3b6432bc909971923d58f9f9af710a16e
Timestamp: 1740724938 Timestamp [UCT]: 2025-02-28 06:42:18 Age [y:d:h:m:s]: 00:266:14:34:56
Block: 1228904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188310 RingCT/type: yes/0
Extra: 01dd2b21f89ec173f2b8a5d9b9f47d29f3b6432bc909971923d58f9f9af710a16e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4318c60a9d69d952f386b9288f484d53ccba56eb97ba57b109a7aad70392578c 0.600000000000 1715785 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": 1228914, "vin": [ { "gen": { "height": 1228904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4318c60a9d69d952f386b9288f484d53ccba56eb97ba57b109a7aad70392578c" } } ], "extra": [ 1, 221, 43, 33, 248, 158, 193, 115, 242, 184, 165, 217, 185, 244, 125, 41, 243, 182, 67, 43, 201, 9, 151, 25, 35, 213, 143, 159, 154, 247, 16, 161, 110, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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