Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97cb753a34c43c8d447c522e2108adecfb5f9a0d4024c7ce4495e5be749f43b

Tx prefix hash: 5b83615dee8ba1d590ceb288390683fff41b9f9b6bb774fbd907e47f359573a5
Tx public key: 364629a0186292e413e7fe6bacd5ece287ed93c99a42706abf7c5a2aec427263
Timestamp: 1729269149 Timestamp [UCT]: 2024-10-18 16:32:29 Age [y:d:h:m:s]: 00:096:04:15:55
Block: 1134400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68699 RingCT/type: yes/0
Extra: 01364629a0186292e413e7fe6bacd5ece287ed93c99a42706abf7c5a2aec4272630211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa6791fbba527ed956ee736c06c4ce565a4d0a5a82c2976d63c5af7c27007f7b 0.600000000000 1617701 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": 1134410, "vin": [ { "gen": { "height": 1134400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa6791fbba527ed956ee736c06c4ce565a4d0a5a82c2976d63c5af7c27007f7b" } } ], "extra": [ 1, 54, 70, 41, 160, 24, 98, 146, 228, 19, 231, 254, 107, 172, 213, 236, 226, 135, 237, 147, 201, 154, 66, 112, 106, 191, 124, 90, 42, 236, 66, 114, 99, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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