Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd556cad1e045f74c3de5855af9e2a8c11ad434210fb7fd0a93516553233e9a

Tx prefix hash: 9028bf38b05492d9e383b12ec3bc0e0d3bf8e40b568472bf21bc7398d9ef0c16
Tx public key: 5db5f51b1d41ea45dd6b2ac62a09e5fed551e66102657d7fa58c4db9c82b618a
Timestamp: 1751450329 Timestamp [UCT]: 2025-07-02 09:58:49 Age [y:d:h:m:s]: 00:142:04:42:34
Block: 1317153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99860 RingCT/type: yes/0
Extra: 015db5f51b1d41ea45dd6b2ac62a09e5fed551e66102657d7fa58c4db9c82b618a02110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d3a4fbd23b8ffa55ea64d6aa1894609cd5c048a688488a5d86cc70e0076783 0.600000000000 1804818 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": 1317163, "vin": [ { "gen": { "height": 1317153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d3a4fbd23b8ffa55ea64d6aa1894609cd5c048a688488a5d86cc70e0076783" } } ], "extra": [ 1, 93, 181, 245, 27, 29, 65, 234, 69, 221, 107, 42, 198, 42, 9, 229, 254, 213, 81, 230, 97, 2, 101, 125, 127, 165, 140, 77, 185, 200, 43, 97, 138, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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